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

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.


test("loadCommitRange loads with default boundaries (start=0, end=latest)") {
testLoadCommitRange(expectedStartVersion = 0, expectedEndVersion = 2)
test("loadCommitRange throws when no start boundary is provided") {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Dah -- this poor pass through API, eh :/

@allisonport-db allisonport-db merged commit 9357c6f into delta-io:master Dec 5, 2025
20 checks passed
allisonport-db added a commit to allisonport-db/delta that referenced this pull request Dec 5, 2025
…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.

3 participants