Dynamodb local 2.2.0 Bug: Segments

Question

Hey there! I'm noticing what appears to be a bug with[ dynamodb local 2.2.0](https://hub.docker.com/layers/amazon/dynamodb-local/2.2.0/images/sha256-e676825ec23d476c878ac656951ef4b26276d1338911ba342364ac1fc74c92b3?context=explore).

In our code, we supply TotalSegments and Segment for a [parallel Scan](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Scan.html#Scan.ParallelScan) against some table A. Our unit tests would provide TotalSegments: 1, and Segment: 0 against local DynamoDB. In previous versions of local, this would successfully return items from A, but with 2.2.0 nothing is returned.

[Documentation for local scan](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocal.UsageNotes.html#DynamoDBLocal.Differences) makes it appear that results are *still* expected, so is this then a bug introduced by 2.2.0?

Thanks!

Answer

Thank you for highlighting this matter. I've promptly informed our DynamoDB Local team about the recent shift in functionality.

Rest assured, we are actively investigating this issue. Your patience is highly appreciated, and I will personally ensure that you are promptly updated as soon as the issue is resolved.

## Update
This issue has been resolved in version 2.2.1, please upgrade to this or a later version.

Dynamodb local 2.2.0 Bug: Segments

Update

Contenus pertinents