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
8.14
No response
bundled
Discovered in #107081 when adding tests.
When one or both ends of range have default values, they are not correctly stored to correspond to user input in case of open ranges.
PUT idx { "mappings": { "properties": { "my_range": { "type": "long_range" } } } }
Given:
PUT idx/_doc/1 { "my_range": { "gt": null, "lt": 300 } }
This query returns a hit even though the range was specified to exclude the start:
POST idx/_search "query" : { "term" : { "my_range" : { "value": -9223372036854775808 } } }
While this correctly returns 0 hits:
POST idx/_search { "query" : { "term" : { "my_range" : { "value": 300 } } } }
The text was updated successfully, but these errors were encountered:
Pinging @elastic/es-storage-engine (Team:StorageEngine)
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Elasticsearch Version
8.14
Installed Plugins
No response
Java Version
bundled
OS Version
Problem Description
Discovered in #107081 when adding tests.
When one or both ends of range have default values, they are not correctly stored to correspond to user input in case of open ranges.
Steps to Reproduce
Given:
This query returns a hit even though the range was specified to exclude the start:
While this correctly returns 0 hits:
Logs (if relevant)
No response
The text was updated successfully, but these errors were encountered: