-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Implement native support StringView for REGEXP_LIKE
#12897
Conversation
481a393
to
fae6d88
Compare
Signed-off-by: Tai Le Manh <[email protected]>
fae6d88
to
899fb7f
Compare
cc @alamb |
@@ -727,7 +727,7 @@ EXPLAIN SELECT | |||
FROM test; | |||
---- | |||
logical_plan | |||
01)Projection: regexp_like(CAST(test.column1_utf8view AS Utf8), Utf8("^https?://(?:www\.)?([^/]+)/.*$")) AS k | |||
01)Projection: regexp_like(test.column1_utf8view, Utf8("^https?://(?:www\.)?([^/]+)/.*$")) AS k |
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.
❤️
LGTM as well. |
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.
TypeSignature::Exact(vec![LargeUtf8, LargeUtf8]), | ||
TypeSignature::Exact(vec![Utf8View, Utf8, Utf8]), |
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.
I think requiring the flags array to be StringArrray (aka only supporting Utf8
as the third argument) makes lots of sense
Which issue does this PR close?
Closes #11910.
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?