this week so will
> be
> > looking at it then,
> >Kind regards, David.
> >
> >
> > From: Martijn Visser
> > Date: Friday, 5 January 2024 at 14:24
> > To: dev@flink.apache.org
> > Subject: [EXTERNAL] Re: [VOTE] Release flink-connector-jdbc,
query cases, which
> should not take too long, but I am out until Thursday this week so will be
> looking at it then,
>Kind regards, David.
>
>
> From: Martijn Visser
> Date: Friday, 5 January 2024 at 14:24
> To: dev@flink.apache.org
> Subject: [EXTERNAL] Re:
: [EXTERNAL] Re: [VOTE] Release flink-connector-jdbc, release candidate
#1
Hi,
Hmmm, it would have been good to mark the Jira ticket as a Blocker
then for the JDBC connector. Since it's marked as Critical, it doesn't
appear. It has also been open for multiple months, so it doesn't
r
Hi,
Hmmm, it would have been good to mark the Jira ticket as a Blocker
then for the JDBC connector. Since it's marked as Critical, it doesn't
appear. It has also been open for multiple months, so it doesn't
really feel like a Blocker. I'm +0 with including this fix, but then
we should either get t
Thanks for driving this
the thing which makes me thinking about -1 (not sure yet and that's why
asking here) is that there is FLINK-33365 [1]
mentioned as a blocker for JDBC connector release at [2]
Since the reason for that is FLINK-16024 [3] as also was explained in
comments for [1].
So should