You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fluss.apache.org by "loserwang1024 (via GitHub)" <gi...@apache.org> on 2026/08/07 06:09:53 UTC
[I] Paimon schema compatibility check is too strict for comments and options [fluss]
loserwang1024 opened a new issue, #3888:
URL: https://github.com/apache/fluss/issues/3888
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
### Motivation
Currently, Paimon schema compatibility check is too strict for comments and options.
### Solution
The column should be added successfully because table comments, column comments, and ordinary Paimon options do not affect the physical schema compatibility required by Fluss.Physical metadata should still be validated, including:
* Column names, types, nullability, and order
* Bucket and bucket key
* Primary keys
* Partition keys
### 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] Paimon schema compatibility check is too strict for comments and options [fluss]
Posted by "luoyuxia (via GitHub)" <gi...@apache.org>.
luoyuxia closed issue #3888: Paimon schema compatibility check is too strict for comments and options
URL: https://github.com/apache/fluss/issues/3888
--
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