-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[BUG] "arithmetic_exception: long overflow" while running sort query on date field #16709
Comments
[Triage] Can you please share some sample data/commands to re-produce this ?
Output
Thank you |
Hi @prudhvigodithi ,
When we execute the query against all these 14 indices we are getting arithmetic exceptions . This is how we are executing the query.
This is the data distribution on the indices When we tried to execute the same query against smaller dataset(i.e. against 10% of the above mentioned data volume) , we did not face any issues. We are currently using OS version 2.11 & these are sample document Document with dueDate value
Document without dueDate value
|
This may have been fixed by #12676, which was merged for OpenSearch 2.13. Are you able to try upgrading to 2.13 or later and testing? |
Describe the bug
We are getting "arithmetic_exception: long overflow" intermittently when we sort the results on date field.
This is the query we are using:
This is error message :
Related component
Search
To Reproduce
We are using this date format on dueDate field.
This is query
Note: Some of the documents/records that are inserted on the index do have value for dueDate field and some of them do.
We tried changing the date format to this
yyyy-MM-dd HH:mm:ss||yyyy-MM-dd||epoch_millis||strict_date_optional_time
, but still we were getting arithmetic_exception.Expected behavior
We want to sort on date field without having any issues.
Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: