You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fluss.apache.org by "xx789633 (via GitHub)" <gi...@apache.org> on 2025/10/23 12:39:06 UTC
[I] [lake] Secure Lake Catalog Access from Flink [fluss]
xx789633 opened a new issue, #1858:
URL: https://github.com/apache/fluss/issues/1858
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
### Motivation
Secure Lake Catalog Access from Flink
1. When Flink accesses the data lake catalog through Fluss (e.g., in union read), Fluss currently transmits all catalog properties—including sensitive information such as passwords—to Flink for catalog access. To enhance security, it is necessary to exclude these sensitive details from the properties transferred.
2. To enable secure lake catalog access from Flink via Fluss, we should modify the process so that Flink users provide sensitive lake catalog information (e.g., passwords) directly at the time of creating the Fluss catalog.
### Solution
_No response_
### Anything else?
_No response_
### Willingness to contribute
- [x] I'm willing to submit a PR!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [lake] Improve Lake Catalog Access from Flink [fluss]
Posted by "wuchong (via GitHub)" <gi...@apache.org>.
wuchong commented on issue #1858:
URL: https://github.com/apache/fluss/issues/1858#issuecomment-3512531518
@luoyuxia How about we persist all non-sensitive lake properties directly into the Fluss table’s properties (excluding any credentials or other sensitive fields)?
Right now, we have a lot of fragile logic that dynamically appends lake properties during table retrieval. This approach is error-prone and is blocking our ability to support multiple lake formats (e.g., Paimon, Iceberg) or different lake catalogs cleanly.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [lake] Improve Lake Catalog Access from Flink [fluss]
Posted by "luoyuxia (via GitHub)" <gi...@apache.org>.
luoyuxia commented on issue #1858:
URL: https://github.com/apache/fluss/issues/1858#issuecomment-3514614836
Yes, I agree that. I created #1963 to track it
> [@luoyuxia](https://github.com/luoyuxia) How about we persist all non-sensitive lake properties directly into the Fluss table’s properties (excluding any credentials or other sensitive fields)?
>
> Right now, we have a lot of fragile logic that dynamically appends lake properties during table retrieval. This approach is error-prone and is blocking our ability to support multiple lake formats (e.g., Paimon, Iceberg) or different lake catalogs cleanly.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [lake] Improve Lake Catalog Access from Flink [fluss]
Posted by "luoyuxia (via GitHub)" <gi...@apache.org>.
luoyuxia closed issue #1858: [lake] Improve Lake Catalog Access from Flink
URL: https://github.com/apache/fluss/issues/1858
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org