Skip to content
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

KCL 3.0 uses consumerName instead of tableName as a prefix for -CoordinatorState and -WorkerMetricStats ddb tables #1433

Open
saefty opened this issue Jan 20, 2025 · 0 comments

Comments

@saefty
Copy link

saefty commented Jan 20, 2025

Description:

KCL allows to configure the table name of the lease table as mentioned here
https://docs.aws.amazon.com/streams/latest/dev/kcl-dynamoDB.html

You can set a custom table name using configuration.

Example from https://repost.aws/knowledge-center/kinesis-kcl-apps-dynamodb-table
ConfigsBuilder configsBuilder = new ConfigsBuilder(...).tableName(<table_name>); // KCL 2.x

Problem:

  • Application receives access denieds or creates unexpected table naming
  • KCL uses the consumer name for the new CoordinatorState and WorkerMetricStats tables

Suggested Solution:

  • Use overwriten table name for lease table aswell as for the new KCL 3.0 table names
@saefty saefty changed the title KCL 3.0 uses consumerName instead of tableName as a prefix for -CoordinatorState and WorkerMetricStats ddb tables KCL 3.0 uses consumerName instead of tableName as a prefix for -CoordinatorState and -WorkerMetricStats ddb tables Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant