You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @jliu0812, I think that was a holdover from when we were using the same approach for DynamoDB and S3, and in S3 the 'tablename' (i.e. s3object) is case-insensitive.
This is now fixed with 0.5.6, just released. Can you upgrade and verify it now works for you?
When a DynamoDB table has mixed cases, the parser throws a KeyError message.
How to reproduce: Run the following code:
Traceback log:
The text was updated successfully, but these errors were encountered: