Search before asking
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
Search before asking
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:
This issue intentionally remains separate from point lookup because write support has different lifecycle, consistency, and metadata refresh requirements.
Willingness to contribute