Upgrade to KCL v2 #55
Conversation
|
Looks like we're still running into #35 with this. We're still currently having to use a cronjob to restart Logstash every 24 hours, we're looking into this hopefully we can come up with a fix. |
|
Just as an update, we've started implementing a Kinesis input using the new Java plugin API. I've heard from one of the guys working on the KCL that generally when you use the KCL you'd also implement a "stuck shard detector" so I think that's the missing piece of the puzzle here. If I manage to get a stable version of this working I'll see what I can do about getting it out to you all |
|
Hi, do you know if this update to KCL 2.0 will be released? AWS has released support for Enhanced Fan Out which can be consumed only with the KCL 2.0. |
|
I'm keen for this update as well, is there any news on when this might be finished off and merged? |
|
Do you know if this update to KCL 2.0 will be released in the near future? |
|
I'm no longer working at Amazon nor using Kinesis and so have no intention of keeping this MR up to date, apologies. |
Resolves #46.
The way KCL is configured has changed between v1 and v2, configuration values are stored in separate POJOs now so there can't just be a single
additional_optionsblock that allows everything to be changed.Since the consumer now has to instantiate the clients it wants to use itself there will have to be separate configuration values for setting things like Kinesis endpoint (so there has been a regression on items like #49 since #51) -
endpointOverridetakes aURIand unsure how we'd handle that without addingkinesis_endpoint,cloudwatch_endpoint, etc configuration values separately, open to any suggestions if that should be in the scope of this PR.Note: this is a breaking change as it requires the following extra permissions to be added to the IAM role being assumed by logstash:
SubscribeToShardDescribeStreamSummaryDescribeStreamConsumerRegisterStreamConsumer