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? 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,
F
------- Original Message -------
On Thursday, December 1st, 2022 at 16:01, Chesnay Schepler <ches...@apache.org>
wrote:
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 at the
same time there's the externalized variant as a drop-in replacement, and
the 1.17.0 release will not include a ES connector.
The rational was to give users some window to update their projects.
We are now about to externalize a few more connectors (cassandra,
pulsar, jdbc), targeting 1.16 within the next week.
The 1.16.0 release has now been about a month ago; so it hasn't been a
lot of time since then.
I'm now wondering if we could/should treat these connectors as
externalized for 1.16, meaning that we would remove them from the master
branch now, not ship them in 1.17 and move all further development into
the connector repos.
The main benefit is that we won't have to bother with syncing changes
across repos all the time.
We would of course need some sort-of cutoff date for this (December
9th?), to ensure there's still some reasonably large gap left for users
to migrate.
Let me know what you think.
Regards,
Chesnay
