-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
SQL: Remove exception throwing from Analyzer #38208
Labels
Comments
Pinging @elastic/es-search |
costin
added a commit
to costin/elasticsearch
that referenced
this issue
Feb 2, 2019
Instead of throwing an exception, use an unresolved attribute to pass the message to the Verifier. Additionally improve the parser to save the extended source for the Aggregate and OrderBy. Close elastic#38208
costin
added a commit
that referenced
this issue
Feb 3, 2019
Instead of throwing an exception, use an unresolved attribute to pass the message to the Verifier. Additionally improve the parser to save the extended source for the Aggregate and OrderBy. Close #38208
costin
added a commit
to costin/elasticsearch
that referenced
this issue
Feb 3, 2019
Instead of throwing an exception, use an unresolved attribute to pass the message to the Verifier. Additionally improve the parser to save the extended source for the Aggregate and OrderBy. Close elastic#38208 (cherry picked from commit 75f0750)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, there's still a rule that uses exceptions in case of problem - while this achieves the goal, the correct way is to let the Verifier collect all issues and report them in one go.
Additionally the same rule produces an incorrect message:
Which needs fixing.
The text was updated successfully, but these errors were encountered: