Skip to content

Conversation

@allisonport-db
Copy link
Collaborator

Which Delta project/connector is this regarding?

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

Description

How was this patch tested?

Does this PR introduce any user-facing changes?

scottsand-db and others added 3 commits December 4, 2025 16:53
… created table (delta-io#5570)

Use this [link](https://github.com/delta-io/delta/pull/5570/files) to
review incremental changes.
-
[**stack/kernel_uc_returns_max_ratified_version_0_after_create**](delta-io#5570)
[[Files changed](https://github.com/delta-io/delta/pull/5570/files)]

---------

- [ ] Spark
- [ ] Standalone
- [ ] Flink
- [X] Kernel
- [ ] Other (fill in here)

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.

Minor logic change. Updated existing UTs.

No.

(cherry picked from commit d6c53a3)
Use this [link](https://github.com/delta-io/delta/pull/5584/files) to
review incremental changes.
-
[**stack/kernel_revert_catalogManaged_rename**](delta-io#5584)
[[Files changed](https://github.com/delta-io/delta/pull/5584/files)]

---------
Revert catalogManaged feature rename

(cherry picked from commit a7e9d62)
…a-io#5537)

<!--
Thanks for sending a pull request!  Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://github.com/delta-io/delta/blob/master/CONTRIBUTING.md
2. If the PR is unfinished, add '[WIP]' in your PR title, e.g., '[WIP]
Your PR title ...'.
  3. Be sure to keep the PR description updated to reflect all changes.
  4. Please write your PR title to summarize what this PR proposes.
5. If possible, provide a concise example to reproduce the issue for a
faster review.
6. If applicable, include the corresponding issue number in the PR title
and link it in the body.
-->

#### Which Delta project/connector is this regarding?
<!--
Please add the component selected below to the beginning of the pull
request title
For example: [Spark] Title of my pull request
-->

- [ ] Spark
- [ ] Standalone
- [ ] Flink
- [X] Kernel
- [ ] Other (fill in here)

## Description

Currently when building a commit range start boundary is optional and
defaults to 0 when not provided. However, there is no good use-case
during which the start version is not provided so this PR makes it
required. The prior behavior can always be implemented by the caller by
providing version=0 start boundary.

## How was this patch tested?

Updates/adds tests.

(cherry picked from commit 9357c6f)
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.

2 participants