Skip to content

superseded by #749: test(delta-harness): add compatibility and streaming scenarios - #719

Closed
mkuchenbecker wants to merge 15 commits into
linkedin:mkuchenbecker/delta-harness-rtasfrom
mkuchenbecker:mkuchenbecker/delta-harness-compatibility-streaming
Closed

mkuchenbecker wants to merge 15 commits into
linkedin:mkuchenbecker/delta-harness-rtasfrom
mkuchenbecker:mkuchenbecker/delta-harness-compatibility-streaming

Conversation

@mkuchenbecker

@mkuchenbecker mkuchenbecker commented Sep 4, 2026 •

Copy link
Copy Markdown
Collaborator

Superseded

This fork-backed PR is superseded by the same-repository PR #749. Do not reopen this PR. The replacement head and base branches both belong to linkedin/openhouse.

mkuchenbecker and others added 14 commits September 1, 2026 23:53
Add concurrency, locking, streaming, table-evolution, and writer compatibility contracts as an extension of the focused RTAS catalog.

The scenarios prove exact writer outcomes, owned streaming resources, active snapshot stability, and observable follow-up behavior.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Validate compatibility and streaming behavior by running its scenarios instead of restating
its generated catalog entries.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Keep compatibility and streaming behavior with the shared scenario suite while preserving its
package and published names.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Replace the general JDK HTTP helper with a lock-specific client built on
the generated OpenHouse Tables API. Preserve response status and
diagnostic text while using the standard authentication and truststore
path in local and remote environments.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Keep the generated lock client and compatibility scenarios on the
focused RTAS stack while removing unrelated foundation breadth.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

# Conflicts:
#	integrations/spark/delta-harness/src/main/scala/harness/openhouse/Framework.scala
#	integrations/spark/delta-harness/src/main/scala/harness/openhouse/LocalRunner.scala
#	integrations/spark/delta-harness/src/main/scala/harness/openhouse/scenarios/ScenarioKit.scala
Keep compatibility, locking, streaming, and concurrency coverage as an
additive layer over the revised RTAS catalog.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…ecker/delta-harness-compatibility-streaming

# Conflicts:
#	integrations/spark/delta-harness/src/test/scala/harness/framework/RunnerTest.scala
Keep layout expansion, side-table ownership, and table creation helpers
with the compatibility, locking, and streaming scenarios that use them.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@mkuchenbecker mkuchenbecker reopened this Sep 17, 2026
@mkuchenbecker mkuchenbecker changed the title test(delta-harness): add compatibility and streaming scenarios superseded by #749: test(delta-harness): add compatibility and streaming scenarios Sep 18, 2026
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