Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dnm migration test #31027

Closed
wants to merge 39 commits into from
Closed

Conversation

jkosh44
Copy link
Contributor

@jkosh44 jkosh44 commented Jan 13, 2025

Motivation

Tips for reviewer

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

@jkosh44 jkosh44 force-pushed the dnm-migration-test branch from 9ca1474 to 78bb64f Compare January 13, 2025 23:06
Previously, when the `force_source_table_syntax` flag was enabled,
the primary source ingestion collection was not included in the source
exports. This would cause the primary source ingestion collection's
upper and since to be stuck at 0, and it would break some existing
code.

This commit always includes the primary ingestion collection in the
source exports. However, when the `force_source_table_syntax` flag is
enabled, then the source export details are set to
`SourceExportDetails::None`. The result is that all source types with
the flag enabled behave similarly to how multi-output sources behave
with the flag disabled in regard to the primary ingestion collection.
Specifically, their upper's and since's move forward in time and
querying them returns an empty result.

A downside of this commit is that a source ingestion is always
scheduled with the flag enabled, even if there are no table exports.
Previously, they would only be scheduled if there were table exports.

Works towards resolving #MaterializeInc/database-issues/issues/8620
@jkosh44 jkosh44 force-pushed the dnm-migration-test branch from 78bb64f to 70981c0 Compare January 14, 2025 14:54
@jkosh44 jkosh44 closed this Jan 22, 2025
@jkosh44 jkosh44 deleted the dnm-migration-test branch January 22, 2025 19:54
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