Skip to content

[flink] Fix batch fallback generating mixed split types for primary-key tables#3296

Open
matrixsparse wants to merge 1 commit intoapache:mainfrom
matrixsparse:feature/fix-batch-fallback-mixed-splits
Open

[flink] Fix batch fallback generating mixed split types for primary-key tables#3296
matrixsparse wants to merge 1 commit intoapache:mainfrom
matrixsparse:feature/fix-batch-fallback-mixed-splits

Conversation

@matrixsparse
Copy link
Copy Markdown
Contributor

@matrixsparse matrixsparse commented May 10, 2026

Summary

Follow-up fix for #3208.

For primary-key tables in batch mode, when no lake snapshot exists, the previous fallback logic called initPartitionedSplits() / initNonPartitionedSplits(), which internally invokes getSnapshotAndLogSplits(). This method may produce mixed split types — HybridSnapshotLogSplit for buckets with KV snapshots and LogSplit for buckets without — which the Flink connector does not support merging in batch mode.

This fix replaces the fallback path with initLogTablePartitionSplits() / getLogSplit() to generate uniform LogSplit for all buckets, avoiding the mixed split type issue.

Changes

  • Partitioned tables: initPartitionedSplits()initLogTablePartitionSplits()
  • Non-partitioned tables: initNonPartitionedSplits()getLogSplit(null, null)

@matrixsparse matrixsparse force-pushed the feature/fix-batch-fallback-mixed-splits branch from 09b5acd to 7ac1f8c Compare May 10, 2026 07:45
@matrixsparse
Copy link
Copy Markdown
Contributor Author

Hi @luoyuxia, this is a follow-up fix for the mixed split types issue you mentioned in #3208.

Could you PTAL? Thanks! cc @fresh-borzoni

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant