ParallelScan result order from AWS DynamoDB-CodePudding

Consider the following aspects:

Java AWS SDK 1.x
No new register has been put to the table during the tests.
Regardless the number of the parallel segments managed internally in DynamoDB.

Does the parallelScan search from the AWS DynamoDB SDK always return the result on the same order?

CodePudding user response：

The scan order will be the same between calls. All items in the table have an order to them. This is needed for parallel scans and LastEvaluatedKey behaviors to work correctly. You can't anticipate the order but it's necessarily stable between invocations.