-
Notifications
You must be signed in to change notification settings - Fork 5
Upgrade to KCL 2.x #13
Comments
I have not worked on it yet. It'd be great if you can open a PR! |
It looks like the api has changed a fair amount: https://docs.aws.amazon.com/streams/latest/dev/kcl-migration.html, so I don't think it will be possible to support both versions. Is that likely to be a problem? |
I don't think so, I'd rather just support the latest SDK version. |
The problems described in #9 are exacerbated when using the 2.0 client lib. There are now separate callbacks for shard ended and shutdown requested and the issue is still that we can't checkpoint until we know we have completed the records we are processing. There are a couple of options I can think of:
Clearly the first option is the simpler, the second should be the more robust. |
I'd say that we should keep the same behavior in the scope of this change (2.X upgrade). I agree that it'd be nice to implement a more robust termination of streams. We can add more mutable shared state to keep track of pending to commit records and terminate the stream if:
or:
Anyway as I said, I'd do it later, as this change needs to be carefully implemented to avoid race conditions & potential problems. |
Are there any plans to upgrade the version of the KCL used? 2.x adds some additional features that we'd be interested in using.
We'll probably try to build a version that works anyway, but don't want to repeat work that's already being done.
The text was updated successfully, but these errors were encountered: