The GitHub Actions job "CI" on fluss.git/feat/spark-lake-upsert-fallback-hybrid has succeeded. Run started by GitHub user fresh-borzoni (triggered by fresh-borzoni).
Head commit for run: e54d01a14f2b0407bcdcd2f6d2c53fdef30590b9 / Anton Borisov <[email protected]> [spark] Use Fluss kv snapshot in lake-batch fallback When a lake-enabled primary-key table has no lake snapshot yet (e.g. not yet tiered), batch reads fell back to scanning the entire log from EARLIEST for every bucket, ignoring any Fluss kv snapshots that already existed. For tables with kv snapshots taken but no lake snapshot, this re-read all historical changes. Plumb the same per-bucket dispatch that FlussUpsertBatch already uses into FlussLakeUpsertBatch.planFallbackPartitions: hybrid (kv snapshot + log tail bounded by stoppingOffset) where a snapshot exists, log-only from EARLIEST bounded by stoppingOffset otherwise. The reader side (FlussUpsertPartitionReader) already supports both shapes. Extract the dispatch logic into a shared createUpsertPartitions helper on FlussBatch so the regular non-lake path and the lake fallback stay in sync. Report URL: https://github.com/apache/fluss/actions/runs/25871527418 With regards, GitHub Actions via GitBox
