We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
To reproduce: Check out main before #125764 was merged. Run a local ES instance via ./gradlew run and ingest the csv test data:
./gradlew run
./gradlew :x-pack:plugin:esql:qa:testFixtures:loadCsvSpecData --args="http://elastic-admin:elastic-password@localhost:9200"
Run the following query (until it errors, it's slightly non-deterministic):
from * | enrich languages_policy on author.keyword | sort book_no | limit 1
This gives a 400 when it errors. Running with error_trace shows that it's due to a mismatch in data types (originally from a wrong layout):
error_trace
Expected [BYTES_REF] but was [INT] ... Caused by: java.lang.IllegalArgumentException: Expected [BYTES_REF] but was [INT] \tat org.elasticsearch.compute.operator.topn.ValueExtractor.extractorFor(ValueExtractor.java:30) \tat org.elasticsearch.compute.operator.topn.TopNOperator$RowFiller.<init>(TopNOperator.java:150) \tat org.elasticsearch.compute.operator.topn.TopNOperator.addInput(TopNOperator.java:371) \tat org.elasticsearch.compute.operator.Driver.runSingleLoopIteration(Driver.java:276) ...
I believe this IAE should've triggered a 500 response; returning 400 can obscure a bug in the compute engine.
The text was updated successfully, but these errors were encountered:
Pinging @elastic/es-analytical-engine (Team:Analytics)
Sorry, something went wrong.
alex-spies
Successfully merging a pull request may close this issue.
To reproduce: Check out main before #125764 was merged. Run a local ES instance via
./gradlew run
and ingest the csv test data:Run the following query (until it errors, it's slightly non-deterministic):
This gives a 400 when it errors. Running with
error_trace
shows that it's due to a mismatch in data types (originally from a wrong layout):I believe this IAE should've triggered a 500 response; returning 400 can obscure a bug in the compute engine.
The text was updated successfully, but these errors were encountered: