Hi Ferenc,
I think this is indeed an important topic to have a discussion about. It
probably also makes sense to create a FLIP and have a vote on this.
One potential option that we could have is to have a generic option to
refer to external data when specifying a connector option,
like ${file:pat
Hello devs,
I'd like to revive this discussion. There is also a ticket about this effort
for some time [1] and this thing also affects us as well. Right now we have a
custom solution that is similar to "environment variables", but it only can be
used in parts of our downstream product. The main
Hi Fred,
thanks for starting this discussion. I totally agree that this an issue
that the community should solve. It popped up before and is still
unsolved today. Great that you offer your help here. So let's clarify
the implementation details.
1) Global vs. Local solution
Is this a DDL-onl
Hi Fred,
Thanks for raising the discussion! I think the definition of “environment
variable” varies under different context. Under Flink on K8s it means the
environment variable for a container, and if you are a SQL client user it could
refer to environment variable of SQL client, or even the
Hi Fred,
Thanks for opening the discussion. There are probably multiple ways to
solve it, you could also think about addressing this problem in a catalogue
and hide any password/keywords in there. But then again, I do think your
solution could also work and is straightforward.
If there are no peo
