-
Notifications
You must be signed in to change notification settings - Fork 24.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
Exception when using source filtering on a large integer field #32395
Comments
Pinging @elastic/es-search-aggs |
I have a very similar issue, starting from this trivial Java code:
Private method
What it is expected to be the right approach? |
Thanks for reporting this issue. I wonder if we should add to |
Although we allow to index BigInteger and BigDecimal into a keyword field, source filtering on these fields would fail as XContentBuilder was not able to deserialize BigInteger and BigDecimal to json. This modifies XContentBuilder to allow to handle BigInteger and BigDecimal. Closes elastic#32395
Although we allow to index BigInteger and BigDecimal into a keyword field, source filtering on these fields would fail as XContentBuilder was not able to deserialize BigInteger and BigDecimal to json. This modifies XContentBuilder to allow to handle BigInteger and BigDecimal. Closes #32395
Although we allow to index BigInteger and BigDecimal into a keyword field, source filtering on these fields would fail as XContentBuilder was not able to deserialize BigInteger and BigDecimal to json. This modifies XContentBuilder to allow to handle BigInteger and BigDecimal. Closes elastic#32395
Although we allow to index BigInteger and BigDecimal into a keyword field, source filtering on these fields would fail as XContentBuilder was not able to deserialize BigInteger and BigDecimal to json. This modifies XContentBuilder to allow to handle BigInteger and BigDecimal. Closes #32395
Although we allow to index BigInteger and BigDecimal into a keyword field, source filtering on these fields would fail as XContentBuilder was not able to deserialize BigInteger and BigDecimal to json. This modifies XContentBuilder to allow to handle BigInteger and BigDecimal. Closes #32395
Elasticsearch version (
bin/elasticsearch --version
): 6.3.1 using the official docker imagePlugins installed: []
Description of the problem including expected versus actual behavior:
When indexing a document with a large integer field as (with
keyword
mappings`, querying fails with an error when using source filtering.This seems a bit similar to #31853, but different enough that I thought I should open an issue.
Steps to reproduce:
Using source-filtering will result in an exception:
(Using
'_source': ['*']
will result in the same error)Provide logs (if relevant):
When using a scroll query, the server log shows the following error:
The text was updated successfully, but these errors were encountered: