Thanks Mayank for the proposal. I think it's a great addition to Flink to
define secure connectivity in general for table, model and other resources
later on. +1.
Hao
On Fri, May 2, 2025 at 5:32 AM Gustavo de Morais
wrote:
> Hi Mayank,
>
> Thanks for the initiative. Looking at the FLIP, this lo
Hi Mayank,
Thanks for the initiative. Looking at the FLIP, this looks like a
well-thought-out proposal that addresses a clear need for more secure and
reusable external connections in Flink SQL and Table API. Separating
connection details would a valuable improvement.
Best Regards,
Gustavo
Am Fr
Hi Mayank,
Thank you for starting the discussion! In general, I think such functionality
would be a really great addition to Flink.
Could you pls. elaborate a bit more one what is the reason of defining a
`connection` resource on the database level instead of the catalog level?
If I think about `
Hi all,
I would like to open up for discussion a new FLIP-529 [1].
Motivation:
Currently, Flink SQL handles external connectivity by defining endpoints
and credentials in table configuration. This approach prevents reusability
of these connections and makes table definition less secure by exposin
