Regexp UDFs and beginnings of generic vectorization #70
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This brings in all the remaining regexp-involving Trino UDFs (except the overload of regexp_replace that has a lambda argument).
They are implemented with the help of a nascent framework for implementing UDFs by lifting / mapping relatively simple row functions to vectorized operations on columns.
The framework is in its very beginning and still relies on excessive cut-paste-modify activity, but already provides some effort savings.
Improvement advice or discussions from those more experienced with Rust and Arrow will be gladly appreciated and incorporated!