Offer true 64-bit precision for BigDecimal and BigInteger on Elasticsearch

Description

Follow-up to

Apparently Elasticsearch parses input to scaled_float fields as a double before converting it to a BigDecimal, losing some precision in the process: https://github.com/elastic/elasticsearch/pull/37169/files#diff-a93bab596c5a9bf9865003cb82c10c55R339

We should submit a patch to fix that, and adapt our tests accordingly.

See TODOs in BigDecimalFieldTypeDescriptor and DecimalScaleIT in particular.

Environment

None

Status

Assignee

Yoann Rodière

Reporter

Yoann Rodière

Labels

None

Suitable for new contributors

None

Pull Request

None

Feedback Requested

None

Components

Fix versions

Priority

Major
Configure