-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DynamoDB scan and DynamoDB.DocumentClient scan return different results #3299
Comments
Hey @zachary-D, thank-you for reaching out to us with your issue, is there an actual test case that you can provide me? I scanned a table with around 11000 items and got the same result for the both. |
I should be able to, what exactly do you need from me? |
Is it possible for you to create a sample repo to get the same results? |
Your expression attribute values for document client should be a different shape, since document client handles marshalling and un-marshalling for you. You are filtering on a map rather than a string, and not getting any results. When using the document client change ':hash' value to a string, rather than the object you currently have. |
I'll give that a try, thanks! |
This issue has not received a response in 1 week. If you still think there is a problem, please leave a comment to avoid the issue from automatically closing. |
Confirm by changing [ ] to [x] below to ensure that it's a bug:
Describe the bug
Scans with DynamoDB.DocumentClient don't return any values, while scans with identical parameters on DynamoDB return the proper items.
Is the issue in the browser/Node.js?
Node.js
If on Node.js, are you running this on AWS Lambda?
Yes
Details of the browser/Node.js version
serverless framework / AWS lambda, nodejs12.x runtime
SDK version number
v2.689.0
To Reproduce (observed behavior)
Expected behavior
Both scans should return the same items, with the different formatting intended for each. As shown in the screenshot, the doc-scan returns no items.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Similar to #1187, if not the same issue
The text was updated successfully, but these errors were encountered: