I think the reason why its different from the CliFrontend is that the
sql client is way younger and as far as I know never reached
"production" readiness. (as per the docs [1], it's still marked as Beta,
plus see the first "Attention" ;) ).
I think it certainly makes sense to have a proper securit
Thanks Dawid,
I think you are right that most of the things should work like this just
fine. Maybe some catalogs will need this at some point but not right now,
I was just wondering why is this different from how the CliFrontend works
which also installs the security context on the Client side.
I
Hi Gyula,
As far as I can tell SQL cli does not support Kerberos natively. SQL CLI
submits all the queries to a running Flink cluster. Therefore if you
kerberize the cluster the queries will use that configuration.
On a different note. Out of curiosity. What would you expect the SQL CLI
to use th
Hi!
Does the SQL CLI support Kerberos Authentication?
I am struggling to find any use of the SecurityContext in the SQL CLI logic
but maybe I am looking in the wrong place.
Thank you!
Gyula
