-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Handling big longs/ integers by REST layer #61109
Comments
Pinging @elastic/es-search (:Search/Search) |
Pinging @elastic/es-core-infra (:Core/Infra/REST API) |
But also how these big integers are sent to Elasticsearch :) In addition to what we said in #32434, I think that supporting bigint as strings in the rest layer it's important for Elasticseach, as one of its best features is that it's very easy to connect to it with any language/platform. Maintaining this interoperability would allow having enough flexibility to support any use case, and keeping the getting started experience flawlessly. What do you think? |
I'm hesitant to have a flag that is supposed to work across the entire REST response. It is really the responsibility of the code writing each section of the response to determine the appropriate format. This seems very similar to me to the print format for date fields, where each individual date field controls how it is printed. That would be a more direct and easy approach to returning bigints as strings since field mappers already have the concept of formatting a value from a field. |
This has been open for quite a while, and hasn't had a lot of interest. For now I'm going to close this as something we aren't planning on implementing. We can re-open it later if needed. |
Some ES clients can't handle well big integers that ES server may pass to them. For example:
It would be nice if a client can tell the ES server in what form it expects these big integers to be returned.
As an example, I am adding @ezimuel suggestion here:
The text was updated successfully, but these errors were encountered: