luoyuxia opened a new issue, #2961:
URL: https://github.com/apache/fluss/issues/2961

   ## Search before asking
   - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and 
found nothing similar.
   
   ## Fluss version
   main (development)
   
   ## Please describe the bug 🐞
   For log tables without a bucket key, enabling lakehouse is currently 
rejected if the table was created before the cluster-level lakehouse mode was 
enabled.
   
   The current validation was introduced to keep Fluss data distribution 
aligned with Paimon. That requirement makes sense for tables with a bucket key, 
where we want the bucket distribution to stay consistent between Fluss and 
Paimon.
   
   However, for log tables without a bucket key, this restriction is 
unnecessarily strict. In this case we do not rely on distribution consistency 
with Paimon, so these tables should still be allowed to enable lakehouse even 
if they were created before lakehouse was enabled at the cluster level.
   
   ### Reproduction
   1. Create a log table without a bucket key while cluster-level lakehouse is 
disabled.
   2. Enable lakehouse at the cluster level.
   3. Try to enable lakehouse for the previously created log table.
   4. Observe that the operation is rejected.
   
   ### Expected behavior
   Lakehouse should be allowed for legacy log tables without a bucket key.
   
   ### Actual behavior
   The current validation rejects enabling lakehouse for these tables.
   
   ## Solution
   Relax the validation for legacy log tables without a bucket key:
   
   - keep the existing distribution-consistency check for log tables with a 
bucket key;
   - allow enabling lakehouse for log tables without a bucket key, even if the 
table was created before cluster-level lakehouse was enabled.
   
   ## Are you willing to submit a PR?
   - [ ] 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to