Issue with DynamoDB as a source and composite keys

Summary

Users are facing issues with using DynamoDB as a source due to problems with composite partition and sort keys, as well as ‘Only top-level primary keys are supported’ errors with certain destinations.


Question

Anyone got dynamodb as a source working? Seems like there’s been a somewhat longstanding issue around using composite partition and sort keys and Only top-level primary keys are supported issues with some destinations.



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["dynamodb", "source", "composite-keys", "primary-keys", "destinations"]

Hi <@U069EMNRPA4>
I’m facing the same issue.
Do you have any information about this? I see that an issue has been opened on https://github.com/airbytehq/airbyte/issues/30250|Github but no news since March

Ooooof this thing is 2 years old :eyes: and java.

So bad news is you’re right, it needs TLC. Good news is that we’ve finally got to a point where we are more comfortable accepting contributions to more complex connectors.

I would be curious to see if I (or anyone here) would be able to just re-implement source-dynamodb in python or Kotlin on top of a fresh CDK version.

The whole connector seems to be around 1k Java LOC