loserwang1024 opened a new issue, #3423: URL: https://github.com/apache/fluss/issues/3423
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Fluss version 0.9.0 (latest release) ### Please describe the bug š Our system supports schema evolution: when a new column is added to the table schema, existing data files are not rewrittenāinstead, the query engine handles missing columns by injecting NULL or default values at read time (client-side compatibility). This works correctly in most scenarios. However, when projection pushdown is applied and the query explicitly selects the newly added column, the scan operator may attempt to read the column directly from storageādespite its absence in old data filesāleading to a failure because the column vector is missing in the batch. ### Solution _No response_ ### 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]
