Skip to content

Conversation

@scottsand-db
Copy link
Collaborator

@scottsand-db scottsand-db commented Nov 24, 2025

🥞 Stacked PR

Use this link to review incremental changes.


Which Delta project/connector is this regarding?

  • Spark
  • Standalone
  • Flink
  • Kernel
  • Other (fill in here)

Description

UC now returns 0 as the maxCatalogVersion for newly created tables, instead of -1.

This PR removes code that handled such cases (mapping -1 to the "true" version of 0).

While we're at it, also does some minor test cleanup and refactors.

How was this patch tested?

Minor logic change. Updated existing UTs.

Does this PR introduce any user-facing changes?

No.

@scottsand-db scottsand-db changed the title done first pass [Kernel] [UC] Handle UC now returning maxCatalogVersion 0 for a newly created table Nov 24, 2025
@scottsand-db scottsand-db self-assigned this Nov 24, 2025
* As of this writing, UC catalog service is not informed when 0.json is successfully written
* during table creation. Thus, when 0.json exists, the max ratified version returned by UC is -1.
*/
private long getTrueUCTableVersion(String ucTableId, long maxRatifiedVersion) {
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the only real change here. Everything else is just test refactors. Thought I'd bundle them all together since it's a rather small PR


val result0 = ucCatalogManagedClient
.buildCreateTableTransaction("ucTableId", tablePath, testSchema, "test-engine")
.buildCreateTableTransaction("testUcTableId", tablePath, testSchema, "test-engine")
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also rename to testUcTableId for clarity; and to align with other test suites

@scottsand-db scottsand-db force-pushed the stack/kernel_uc_returns_max_ratified_version_0_after_create branch from 08a00b4 to 6501575 Compare November 25, 2025 16:28
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