-
Notifications
You must be signed in to change notification settings - Fork 0
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
Dev highlight in ppl #106
Dev highlight in ppl #106
Conversation
…roject. Signed-off-by: forestmvey <forestv@bitquilltech.com>
Signed-off-by: forestmvey <forestv@bitquilltech.com>
Signed-off-by: forestmvey <forestv@bitquilltech.com>
…quotes. Signed-off-by: forestmvey <forestv@bitquilltech.com>
Signed-off-by: forestmvey <forestv@bitquilltech.com>
Signed-off-by: forestmvey <forestv@bitquilltech.com>
public LogicalPlan visitHighlight(Highlight node, AnalysisContext context) { | ||
LogicalPlan child = node.getChild().get(0).accept(this, context); | ||
|
||
if (!(((Alias)node.getExpression()).getDelegated() instanceof HighlightFunction)) { |
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.
Is this defensive check or is this situation possible?
Can the code be updated so that (Alias)
casts and instanceof
checks are not necessary?
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 don't believe this situation would be possible. I have removed the instanceof
check and I wasn't able to figure out a way to update the code to not use casting.
Description
Add PPL support for highlight in SQL plugin.
Issues Resolved
Issue: github-636
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.