-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Fix StatementParserTests #129898
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
Fix StatementParserTests #129898
Conversation
This change fixes StatementParserTests.testPreserveParanthesis as it now depends on capability enabled only on snapshot builds
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
astefan
left a comment
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
| public void testSubqueryWithPipe() { | ||
| assumeTrue("Requires EXPLAIN capability", EsqlCapabilities.Cap.EXPLAIN.isEnabled()); | ||
| assertEquals(new Explain(EMPTY, PROCESSING_CMD_INPUT), statement("explain ( row a = 1 )")); | ||
| } |
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.
testSubquery and testSubqueryWithPipe are identical now. I am keeping only one of them.
luigidellaquila
left a comment
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 @idegtiarenko, LGTM
This change fixes StatementParserTests.testPreserveParanthesis as it now depends on capability enabled only on snapshot builds
This change fixes StatementParserTests.testPreserveParanthesis as it now depends on capability enabled only on snapshot builds
Closes: #129887
Related to: #129526