[default values] Move read-bridge column-default ramp into OpenHouse - #674
Open
cbb330 wants to merge 7 commits into
Open
[default values] Move read-bridge column-default ramp into OpenHouse#674cbb330 wants to merge 7 commits into
cbb330 wants to merge 7 commits into
Conversation
This was referenced Aug 12, 2026
Collaborator
Author
|
Next in stack: #675 ( |
cbb330
force-pushed
the
chbush/read-bridge-policy-ramp
branch
from
August 12, 2026 02:24
e145421 to
72f4fa5
Compare
cbb330
force-pushed
the
chbush/read-bridge-policy-ramp
branch
from
August 12, 2026 04:55
72f4fa5 to
1f23dad
Compare
cbb330
marked this pull request as ready for review
August 12, 2026 05:34
cbb330
force-pushed
the
chbush/read-bridge-policy-ramp
branch
from
August 12, 2026 16:51
59b8423 to
33ddb7a
Compare
This was referenced Aug 12, 2026
cbb330
force-pushed
the
chbush/read-bridge-policy-ramp
branch
from
August 13, 2026 05:42
ab56db9 to
d5faa07
Compare
17 tasks
cbb330
force-pushed
the
chbush/read-bridge-policy-ramp
branch
from
August 13, 2026 06:10
d5faa07 to
b0fbf21
Compare
| e); | ||
| return Collections.emptyMap(); | ||
| } | ||
| if (columnDefaults == null || columnDefaults.isEmpty()) { |
Contributor
There was a problem hiding this comment.
Why let column defults be nullable?
Collaborator
Author
There was a problem hiding this comment.
this is a stub right now and will be changed in follow up PRs
Keep the deployment-specific ColumnDefaultsSource optional and data-only; OpenHouse owns the read-bridge.column-default feature id, self-serve enabled property, and fail-open toggle lookup before asking for defaults.
Correct the self-service property name and drop the contradictory "cluster kill switch" claim. Add coverage for a real source that returns no defaults, and assert table-property opt-in never calls the server toggle. Testing Done: - :services:tables:test --tests '*ReadBridgeConfigResolverTest'
BaseTableFeatureToggle looks up (databaseId, tableId, featureId) exactly; claiming a * / * fleet kill switch was inaccurate. Also note HTS is only hit when the self-service property is absent.
Replace essay javadoc with brief ownership, contract, ObjectProvider, and fail-open notes so the PR description carries the design narrative.
cbb330
force-pushed
the
chbush/read-bridge-policy-ramp
branch
from
August 13, 2026 23:55
b0fbf21 to
ea956d9
Compare
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Depends on #668 (stacked on #645).
Move column-default rollout policy into OpenHouse so a deployment only supplies the defaults themselves.
ReadBridgeConfigResolver)TableFeatureToggle+ table property)ColumnDefaultsSource, e.g. LI ASL)Ids (one token, capability-scoped — not bare
read-bridge):read-bridge.column-defaultread-bridge.column-default.enabledopenhouse.read-bridge.column-default.<fieldId>Resolve flow
On get/create/update,
withConfigcallsReadBridgeConfigResolver.resolve(tableDto):ColumnDefaultsSource.NONE) → empty config, no HTS callfalse, or HTS notACTIVE, or HTS error) → empty config; source not consultedopenhouse.read-bridge.column-default.<fieldId> = <single-value-json>Self-serve override (
isFeatureActivatedWithOverride):true/false→ table wins, HTS skipped(databaseId, tableId, featureId)Changes
ApiConfigwires resolver viaObjectProvider<ColumnDefaultsSource>(no@ConditionalOnMissingBeannoop / no@Primary);resolve(TableDto)only*.enabledoverride; fail-open on toggle lookup errorsColumnDefaultsSourceis data-only; ramp is not the deployment’s job*/*today) and when HTS is hitReadBridgeConfigResolverTestcovers inert/no-source, fail-open, opt-in/out, empty source, stamp, handlerconfig;ReadBridgeColumnDefaultE2ETestis HTTP create/get with a stub source (property / HTS / fail-closed)Why these choices
read-bridge/v3-read-bridgeleft free for a later superset.NONE— avoids competing default beans when a deployment registers its source with@Bean.Ops notes
(databaseId, tableId, featureId)viaBaseTableFeatureToggle. There is no glob*/*fleet rule yet; fleet ramp means per-tableACTIVErows and/or the table property.read-bridge.column-default.enabledis absent, resolve can hit HouseTables on the read path. When the property is present, HTS is skipped.Testing Done
./gradlew :services:tables:test --tests '*ReadBridgeConfigResolverTest' --tests '*ReadBridgeColumnDefaultE2ETest'Additional Information
Stack
ReadBridge.applyclient overlayLI follow-ups (data-only source): #2204 → #2203
Rollback Plan
Revert this PR. Deployments without a
ColumnDefaultsSourcestill stamp nothing. Toggle fail-open keeps reads at today’s NULL behavior if HTS is unhealthy.