-
Notifications
You must be signed in to change notification settings - Fork 79
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
Kinesis Application State in Dynamo DB #22
Comments
Kinesis SQL library does not use KCL for most of its working. KCL and structured streaming APIs does not go along so well. Also, KCL comes with an extra cost of DynamoDB which can be avoided for structured streaming But at the same time, while designing kinesis-sql, we knew that users would want more reliable shard progress committer. Hence the module provides an option of pluggable committer. We can do the following to use another committer
I am relying on the community to implement dynamodb committer. cc @VikramBPurohit |
Hi @itsvikramagr,
Thanks again for writing this library and providing constant support to community.
Our spark structure streaming code doesn't need to be stateful. We are ok with cluster or executors going down as long as Kinesis is managing consumer's application state.
https://docs.aws.amazon.com/streams/latest/dev/kinesis-record-processor-ddb.html
Could you shed some light on -
Thanks in advance for your response!
The text was updated successfully, but these errors were encountered: