Skip to content

Fix View.verifyConfig mutating caller-shared bigquery configs - #2273

Merged
rafal-hawrylak merged 1 commit into
mainfrom
fix-view-shared-config
Sep 3, 2026
Merged

rafal-hawrylak merged 1 commit into
mainfrom
fix-view-shared-config

Conversation

@rafal-hawrylak

Copy link
Copy Markdown
Collaborator

Shallow-clone unverifiedConfig.bigquery before the hoist-then-delete loop so a shared bigquery object is not stripped across successive publish() calls. View.verifyConfig has its own hoist-then-delete loop outside LegacyConfigConverter; #2260 fixed the converter, which covers Table and IncrementalTable but not View.

Fixes #2267.

Shallow-clone unverifiedConfig.bigquery before the hoist-then-delete
loop so a shared `bigquery` object is not stripped across successive
publish() calls. View.verifyConfig has its own hoist-then-delete loop
outside LegacyConfigConverter; #2260 fixed the converter, which
covers Table and IncrementalTable but not View.

Fixes #2267.
@rafal-hawrylak
rafal-hawrylak merged commit 9c74268 into main Sep 3, 2026
11 checks passed
@rafal-hawrylak
rafal-hawrylak deleted the fix-view-shared-config branch September 3, 2026 22:24
rafal-hawrylak added a commit that referenced this pull request Sep 7, 2026
Bumps the npm package version to release two shared-config mutation
fixes (#2273 View.verifyConfig, #2283 Session.declare — both stop
in-place hoists/deletes from stripping fields off a caller-held config)
alongside the PropertyGraph improvements from #2275 (tags support) and
#2281 (preserve explicit includeDependentAssertions=false).
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.

#2260 does not cover views — a shared config object still loses bigquery.partitionBy / clusterBy across publish() calls

2 participants