-
Notifications
You must be signed in to change notification settings - Fork 206
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
[BUG] LeaderPartition cannot be cast to StreamPartition #5167
Comments
Hi @vincentpham13, The dynamodb source currently requires enabling source coordination with DynamoDB as a store. The If you plan on scaling Data Prepper horizontally, then using DynamoDB as a store with source coordination is a requirement regardless of the in_memory store not being supported. Please see the documentation that I shared above for how to configure DynamoDB as a source coordination store in the |
Hi @graytaylor0, Thank you for your reply. After configuring the source coordination with DynamoDB as the store, this issue has been resolved. I have another issue I hope you can help with. As I mentioned, I'm testing with DynamoDB local. The problem is that the Data Prepper server attempts to use the endpoint dynamodb.ddblocal.amazonaws.com, where ddblocal is the region automatically created when using DynamoDB local. Here is full logs
|
Describe the bug
I'm using docker compose which starts an opensearch node and a data-prepper server.
My pipeline is using DynamoDB (AWS not Local) as
source
, the created opensearch node assink
.The error is about casting a value from the LeaderPartition type to the StreamPartition type.
To Reproduce
Steps to reproduce the behavior:
docker compose up -d --build
to starts all needed servicesdocker logs -f docker-dynamodb-opensearch-data-prepper-opensearch-data-prepper-1
Expected behavior
data-prepper server is ready to consume records from DynamoDB stream, then write to Opensearch index
Screenshots
Environment (please complete the following information):
Additional context
docker-compose.yml
data-prepper-config.yaml
pipelines.yaml
The text was updated successfully, but these errors were encountered: