-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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] mapper_parsing_exception: No handler for type [unsigned_long] declared #2083
Comments
According to the Elastic documentation it was part of X-Pack, which was not APLv2. Should we turn this into a feature request? |
@slavafomin Hi! Would you mind adding more information about your use case? Thanks! |
Just ran into this as well trying to migrate from ES to opensearch. I guess the work around is to use a long? |
We have a use case: we are trying to save the result of XXHash algorithm as a number property, and the output of the algorithm is of type unsigned long. These are too big for the long range and these indexing operations fail as a result. |
@ywilkof may I ask you please to share a bit more how you use |
Correct, assuming the value fits into |
I will add to the use-cases where unsigned values are important. It is very common for IT observabillity-related metrics to be counters, which by definition are unsigned values. In particular for network devices high-capacity, 64-bit counters are common. While 63-bits (the maximum positive value of a 64-bit signed integer) is a very large value, a 400Gb interface's count of bytes can reach the limit of a |
Describe the bug
I've tried to create an index field of the type
unsigned_long
, but got the following error:Host/Environment (please complete the following information):
I'm using latest version of OpenSearch (1.1) managed by AWS.
Additional context
The
unsigned_long
type is defined in ElasticSearch 7.10 documentation. Isn't OpenSearch based on it?The text was updated successfully, but these errors were encountered: