-
Notifications
You must be signed in to change notification settings - Fork 240
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use faster multi-contains in rlike
regex rewrite
#11810
Merged
thirtiseven
merged 8 commits into
NVIDIA:branch-25.02
from
thirtiseven:multiple_contains_write
Dec 19, 2024
+35
−25
Merged
Changes from 4 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
cedcd58
use multiple contains in rlike rewrite
thirtiseven 14900dd
memory leak
thirtiseven ee65a32
address comment
thirtiseven 24e75a2
save a temp columnvector
thirtiseven ca1ba0c
foreach
thirtiseven c84e05e
foldLeft again
thirtiseven 4f33192
withResource
thirtiseven 613cb1e
Use AST
thirtiseven File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still has not closed item.
outputs:
Your approach closed 3 times, but we need to close 4 times(including the intermediate result)
Items need to close: 1, 2, 5 and 3(intermediate result)
Do the following chang:
==>>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we just do a for loop. We are trying really hard to do something fancy when we can just make it simple.
Once we have that working, then you can play around with ways to make it cleaner and/or faster.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for my previous comment
Haoyang's method is right, I ignored that
withResource(boolCvs.tail)
will close multiple times if boolCvs.size > 3.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Talked with @res-life offline, we think the following method is correct:
because all elements in
boolCvs.tail
can be closed in outerwithResource
,boolCvs.head
and intermediate results are closed in innerwithResource
.But your approach looks better because it can close items in
boolCvs
earlier after use, so the memory usage is less. Updated to this method with some changes.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok updated again, this should be cleaner and close values as early as the
foreach
method:please take a look.