Skip to content
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

ESQL: fix csv-spec tests expecting a floating result #108560

Open
bpintea opened this issue May 13, 2024 · 5 comments
Open

ESQL: fix csv-spec tests expecting a floating result #108560

bpintea opened this issue May 13, 2024 · 5 comments
Labels
:Analytics/ES|QL AKA ESQL >bug Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) >test Issues or PRs that are addressing/adding tests

Comments

@bpintea
Copy link
Contributor

bpintea commented May 13, 2024

Description

Some tests expecting a floating point result can fail on equality matching.
We should either include in the query a rounding call for them all, or fix the infra to do a range check instead of an exact one.

@bpintea bpintea added >bug >test Issues or PRs that are addressing/adding tests :Analytics/ES|QL AKA ESQL labels May 13, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-analytical-engine (Team:Analytics)

@elasticsearchmachine elasticsearchmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label May 13, 2024
@alex-spies
Copy link
Contributor

This problem also occurs with queries that create geo POINTs as output; didn't fail us any tests yet, but at least incurs some noise in PRs that touch geo optimizations, like here.

@luigidellaquila
Copy link
Contributor

IMHO it's hard to define a single rounding criterion that can be applied to all the spec tests, in some cases we really want to test that the result is really accurate.
As a first step we could at least reduce the noise by manually rounding the most problematic cases

elasticsearchmachine pushed a commit that referenced this issue May 21, 2024
The test failed repeatedly due to small differences in the final result,
especially in multi-node. These differences are only due to the order of
double operations

https://gradle-enterprise.elastic.co/s/yke3pbfiqsvfo/console-log?page=5
https://gradle-enterprise.elastic.co/s/yjustunaoqnss/console-log?anchor=4650&page=5

Related to #108560
luigidellaquila added a commit to luigidellaquila/elasticsearch that referenced this issue May 21, 2024
The test failed repeatedly due to small differences in the final result,
especially in multi-node. These differences are only due to the order of
double operations

https://gradle-enterprise.elastic.co/s/yke3pbfiqsvfo/console-log?page=5
https://gradle-enterprise.elastic.co/s/yjustunaoqnss/console-log?anchor=4650&page=5

Related to elastic#108560
elasticsearchmachine pushed a commit that referenced this issue May 21, 2024
The test failed repeatedly due to small differences in the final result,
especially in multi-node. These differences are only due to the order of
double operations

https://gradle-enterprise.elastic.co/s/yke3pbfiqsvfo/console-log?page=5
https://gradle-enterprise.elastic.co/s/yjustunaoqnss/console-log?anchor=4650&page=5

Related to #108560
jedrazb pushed a commit to jedrazb/elasticsearch that referenced this issue May 21, 2024
The test failed repeatedly due to small differences in the final result,
especially in multi-node. These differences are only due to the order of
double operations

https://gradle-enterprise.elastic.co/s/yke3pbfiqsvfo/console-log?page=5
https://gradle-enterprise.elastic.co/s/yjustunaoqnss/console-log?anchor=4650&page=5

Related to elastic#108560
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/ES|QL AKA ESQL >bug Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) >test Issues or PRs that are addressing/adding tests
Projects
None yet
Development

No branches or pull requests

5 participants