-
Notifications
You must be signed in to change notification settings - Fork 40
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
Include expression parsers for HashAggregate and ObjectHashAggregate #1432
Conversation
Signed-off-by: Niranjan Artal <[email protected]>
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 an old bug or a bug introduced during the last refactor? I wonder we did not notice that from the tests.
@@ -59,7 +59,7 @@ class GenericExecParser( | |||
} | |||
|
|||
protected def getExprString: String = { | |||
node.desc.replaceFirst(s"${node.name} ", "") | |||
node.desc.replaceFirst(s"${node.name}\\s*", "") |
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.
Yeah I remember seeing HashAggregate(
in the description
QQ: Is it possible that the node.name
may not come at the beginning of the node description?
In that case we better use a regex ^(node_name)\\s*
to guarantee that we replace node_name when it is at the beginning of the description.
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.
Thanks @amahussein ! Updated it. Adding of expression parsers was missed during refactoring. Since we are getting the expressions in #1431, we should be able to update some of the tests to capture these kinds of bugs.
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.
Thanks @nartal1 !
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.
Thanks @nartal1. LGTME.
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.
Thanks @nartal1 !
This is a bug fix. This was missed while refactoring Exec Parser PR - #1396
Changes in this PR :