luoyuxia opened a new issue, #3633: URL: https://github.com/apache/fluss/issues/3633
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Description Parent issue: #3631 Support writing records that target historical partitions for datalake-enabled tables. After point lookup support is available, the remaining FIP-28 work is to define and implement the write path for records whose partition no longer exists as an active Fluss partition but still exists in lake storage. The implementation should cover: - The expected semantics for writes targeting historical partitions, including whether the write should update lake storage directly, recreate Fluss-side metadata, or be rejected under specific conditions. - Metadata refresh/lifecycle behavior needed once historical partition writes are supported. - Integration with partition resolution in writers. - Lake-format-specific implementation, starting with Paimon. - Tests for accepted writes, rejected writes, schema evolution, and lookup-after-write behavior. This issue intentionally remains separate from point lookup because write support has different lifecycle, consistency, and metadata refresh requirements. ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
