Hi all,
+1 (non-binding), I agree that syncing the changes going forward would be a
huge effort and a cutoff date makes sense.
Best,
Mason
On Tue, Dec 6, 2022 at 12:10 AM Ryan Skraba
wrote:
> Hello -- this makes sense to me: removing connectors from 1.17 (but not the
> 1.16 branch) will still
Hello -- this makes sense to me: removing connectors from 1.17 (but not the
1.16 branch) will still give users a long time to migrate.
+1 (non-binding)
Ryan
On Fri, Dec 2, 2022 at 11:42 AM Dong Lin wrote:
> Sounds good!
>
> +1
>
> On Fri, Dec 2, 2022 at 5:58 PM Chesnay Schepler
> wrote:
>
> >
Sounds good!
+1
On Fri, Dec 2, 2022 at 5:58 PM Chesnay Schepler wrote:
> Dec 9th is just a suggestion; the idea being to have a date that covers
> connectors that are being released right now, while enforcing some
> migration window.
>
> We will not reserve time for such a verification. Release
The list of connectors were just those that I'm aware of. Any connector
that meets the deadline would be included in this proposal.
On 01/12/2022 22:30, Ferenc Csaky wrote:
Hi!
I think this would be a good idea. I was wondering that could we include the
hbase connector to this group as well?
Dec 9th is just a suggestion; the idea being to have a date that covers
connectors that are being released right now, while enforcing some
migration window.
We will not reserve time for such a verification. Release testing is
meant to achieve that.
Since 1.16.x is unaffected by the removal fro
Hello Chesney,
The overall plan sounds good! Just to double check, is Dec 9th the proposed
cutoff date for the release of those externalized connectors?
Also, will we reserve time for users to verify that the drop-in replacement
from Flink 1.16 to those externalized connectors can work as expecte
Hi!
I think this would be a good idea. I was wondering that could we include the
hbase connector to this group as well? The externalization PR [1] should be in
a good shape now and Dec 9th as a release date sounds doable.
WDYT?
[1] https://github.com/apache/flink-connector-hbase/pull/2
Best,
Hello,
+1
I was thinking the same. With regard to the cut off date I would be
inclined to be more aggressive and say feature freeze for 1.17. Users do
not *need* to migrate for 1.16.
Thanks
On Thu, 1 Dec 2022, 15:01 Chesnay Schepler, wrote:
> Hello,
>
> let me clarify the title first.
>
> In
Hello,
let me clarify the title first.
In the original proposal for the connector externalization we said that
an externalized connector has to exist in parallel with the version
shipped in the main Flink release for 1 cycle.
For example, 1.16.0 shipped with the elasticsearch connector, but
