Dynamodb local 2.2.0 Bug: Segments

0

Hey there! I'm noticing what appears to be a bug with dynamodb local 2.2.0.

In our code, we supply TotalSegments and Segment for a parallel Scan 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 makes it appear that results are still expected, so is this then a bug introduced by 2.2.0?

Thanks!

  • The version 2.2.1 addresses this change in functionality, released 2024-01-04

PG-Soul
asked 2 months ago208 views
1 Answer
1

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.

profile pictureAWS
EXPERT
answered 2 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions