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
Our team is looking to use Shedlock for task scheduling in our project, and we plan to use DynamoDB as our database. We have identified a few areas where the Shedlock DynamoDB provider could be improved:
Custom Partition Key Name: Currently, the partition key name in the DynamoDB provider is static and set to _id. This limitation poses a challenge for us as we have existing tables in production where the partition key is named differently. It would be helpful if the partition key name could be passed as a parameter when initializing the DynamoDB provider. This flexibility would allow us to utilize our existing tables without having to modify them.
Support for DynamoDBAsyncClient: In our Spring WebFlux project, we use non-blocking code extensively and have a DynamoDbAsyncClient bean for interacting with DynamoDB. However, Shedlock does not currently support the DynamoDbAsyncClient, necessitating the creation of an additional DynamoDB client bean specifically for Shedlock. It would be beneficial if the DynamoDB provider could be updated to support both DynamoDbClient and DynamoDbAsyncClient, enabling us to maintain a fully non-blocking architecture.
if you need any support or assistance in implementing these features, I would be happy to contribute to the development effort.
Thanks!
The text was updated successfully, but these errors were encountered:
Hello @lukas-krecan
Our team is looking to use Shedlock for task scheduling in our project, and we plan to use DynamoDB as our database. We have identified a few areas where the Shedlock DynamoDB provider could be improved:
Custom Partition Key Name: Currently, the partition key name in the DynamoDB provider is static and set to _id. This limitation poses a challenge for us as we have existing tables in production where the partition key is named differently. It would be helpful if the partition key name could be passed as a parameter when initializing the DynamoDB provider. This flexibility would allow us to utilize our existing tables without having to modify them.
Support for DynamoDBAsyncClient: In our Spring WebFlux project, we use non-blocking code extensively and have a DynamoDbAsyncClient bean for interacting with DynamoDB. However, Shedlock does not currently support the DynamoDbAsyncClient, necessitating the creation of an additional DynamoDB client bean specifically for Shedlock. It would be beneficial if the DynamoDB provider could be updated to support both DynamoDbClient and DynamoDbAsyncClient, enabling us to maintain a fully non-blocking architecture.
if you need any support or assistance in implementing these features, I would be happy to contribute to the development effort.
Thanks!
The text was updated successfully, but these errors were encountered: