You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fluss.apache.org by "benqwu (via GitHub)" <gi...@apache.org> on 2025/09/28 06:05:50 UTC
[I] Can the Fluss cluster change the datalake configuration from the cluster level to the table level? [fluss]
benqwu opened a new issue, #1767:
URL: https://github.com/apache/fluss/issues/1767
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
### Motivation
The datalake configuration of the current Fluss cluster requires specifying datalake.format in server.yml, which means a single Fluss cluster can only use one datalake format. If multiple datalake formats need to be used simultaneously, multiple Fluss clusters must be deployed.
If the datalake configuration is changed from the cluster level to the table level, will a single Fluss cluster be able to support multiple datalake formats simultaneously?
### Solution
_No response_
### Anything else?
_No response_
### Willingness to contribute
- [ ] 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] Can the Fluss cluster change the datalake configuration from the cluster level to the table level? [fluss]
Posted by "caozhen1937 (via GitHub)" <gi...@apache.org>.
caozhen1937 commented on issue #1767:
URL: https://github.com/apache/fluss/issues/1767#issuecomment-3342367687
This is a great feature for me. I can assist in designing and implementing this feature.
--
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] Can the Fluss cluster change the datalake configuration from the cluster level to the table level? [fluss]
Posted by "coolderli (via GitHub)" <gi...@apache.org>.
coolderli commented on issue #1767:
URL: https://github.com/apache/fluss/issues/1767#issuecomment-4211002290
I think this is a very important feature.My companies have different lake table formats based on different scenarios, such as Iceberg and Paimon supporting near real time, but Lance doing multimodal. We expect to implement a single table through fluss.
--
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] Can the Fluss cluster change the datalake configuration from the cluster level to the table level? [fluss]
Posted by "MehulBatra (via GitHub)" <gi...@apache.org>.
MehulBatra commented on issue #1767:
URL: https://github.com/apache/fluss/issues/1767#issuecomment-3343632609
Hi @benqwu , currently, we don’t support this feature. Once you select a single table format, it applies to the entire cluster.
That said, I completely understand the need for table-level format selection for individual Fluss tables. We’ll definitely keep this in mind and add it to our feature roadmap.
--
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] Can the Fluss cluster change the datalake configuration from the cluster level to the table level? [fluss]
Posted by "dhama-shashank-meesho (via GitHub) via issues" <is...@fluss.apache.org>.
dhama-shashank-meesho commented on issue #1767:
URL: https://github.com/apache/fluss/issues/1767#issuecomment-6835683050
We're also very interested in this feature, since table-level format selection is important for our production use cases.
@caozhen1937 We'd be glad to contribute the implementation, building on the approach agreed in #2908. We'll raise well-scoped, incremental PRs with tests and docs.
--
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