[BUG] DynamoDB source export converts Numbers ending in 0 to scientific notation

[graytaylor0]

Describe the bug
Given an item in with a Number type ending in 0, such as 1702062202420, the DynamoDB source will convert it to scientific notation for export items.

{"pk": "my_partition_key", "sk":"my_sort_key", "my_number_ending_in_0": 702062202420 }

To Reproduce
Steps to reproduce the behavior:

1. Create a pipeline with a dynamodb source with export and an opensearch
2. Once the export is complete, the document will be sent to the OpenSearch sink as the following with the my_number_ending_in_0 key converted to scientific notation

{"pk": "my_partition_key", "sk":"my_sort_key", "my_number_ending_in_0": 1.70206220242E+12 }

Expected behavior
The Numbers ending in 0 should not be manipulated and the above example should result in

{"pk": "my_partition_key", "sk":"my_sort_key", "my_number_ending_in_0": 702062202420 }

Additional context
The conversion only happens for export values when converting from the ion line here (

data-prepper/data-prepper-plugins/dynamodb-source/src/main/java/org/opensearch/dataprepper/plugins/source/dynamodb/converter/ExportRecordConverter.java

Line 82 in 91ff22d

Map data = (Map<String, Object>) convertToMap(line).get(ITEM_KEY);

), but Data Prepper JacksonEvent also converts to scientific notation when converting to json string (

data-prepper/data-prepper-api/src/main/java/org/opensearch/dataprepper/model/event/JacksonEvent.java

Line 621 in 91ff22d

public String toJsonString() {

). I initially had created a custom deserializer that iterated over and converted all decimals of this format to not use scientific notation, however this may not be the best approach

[san81]

I can work this

[san81]

As part of this change, we provided an option for the user to convert the decimal number to BigDecimal of his own chosen scale (or precision) which should help handle numbers ending in 0 not to get converted into scientific notation. PR notes in the below link has the details about about how to use this and what kind of flexibility user has to tune his needs. Hence marking this ticket as fixed.

#4557

[dlvenable]

The solution to provide a scale is useful, but ideally, the dynamodb source can automatically handle this situation so that customers do not have to add the manual conversions.

[dblock]

[Catch All Triage - 1, 2, 3, 4]