Hi,
I can work on a PR to backport the relevant changes, but it may take a few
days before I get to it.
Thanks,
Thomas
--
sent from mobile
On Mon, Jun 11, 2018, 1:50 PM Tzu-Li (Gordon) Tai
wrote:
> Thanks for bring this up, Bowen.
>
> I’m not sure that it’ll be straightforward to just use
Quick bump:
It should be possible for users still on 1.4.x to just do `mvn clean install
-Daws.kinesis-kpl-version=0.12.6` when building the Kinesis connector, to
upgrade the KPL version used.
I think we should add this to the documentation. Here’s a JIRA to track that -
Thanks for bring this up, Bowen.
I’m not sure that it’ll be straightforward to just use the Kinesis connector in
Flink 1.5 to work with 1.4.
So, +1 to have a backport of necessary changes to allow the Kinesis connector
to continue to work for Flink 1.4, and we proceed with another bug fix
I agree that it would be nice to offer a backport for all 1.4 users. Thomas
would it be possible to contribute the backport back to the community?
Cheers,
Till
On Wed, Jun 6, 2018 at 5:25 PM Thomas Weise wrote:
> -->
>
> On Wed, Jun 6, 2018 at 1:06 AM, Bowen Li wrote:
>
> > Hi,
> >
> > I
-->
On Wed, Jun 6, 2018 at 1:06 AM, Bowen Li wrote:
> Hi,
>
> I think the following email thread might have gone lost.
>
> Dyana brought up the attention that AWS has informed users that KPL
> versions
> < 0.12.6 will *stop working* starting from the 12th of June. Flink 1.4 is
> using KPL
Hi,
I think the following email thread might have gone lost.
Dyana brought up the attention that AWS has informed users that KPL versions
< 0.12.6 will *stop working* starting from the 12th of June. Flink 1.4 is
using KPL 0.12.5 and Flink 1.5 uses 0.12.6, *so Flink 1.4 and below (1.3,
etc) will
