Skip to content

require pre-defined numeric bounds#30

Open
vvv214 wants to merge 1 commit into
google:mainfrom
vvv214:codex/require-public-numeric-bounds
Open

require pre-defined numeric bounds#30
vvv214 wants to merge 1 commit into
google:mainfrom
vvv214:codex/require-public-numeric-bounds

Conversation

@vvv214

@vvv214 vvv214 commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

Require pipeline numerical quantile derivation to use descriptor-supplied NumericalAttribute bounds (following what is done in in-memory path) instead of exact min/max from sensitive data. Missing bounds now raise errors.

Validation: pytest tests/pipeline_transformations/numerical_values_derivation_test.py tests/pipeline_transformations/dataset_encoding_test.py -q passed.

@vvv214 vvv214 force-pushed the codex/require-public-numeric-bounds branch 4 times, most recently from 89f0e4e to 33b79df Compare July 2, 2026 16:14
@vvv214 vvv214 changed the title [codex] require public numeric bounds require pre-defined numeric bounds Jul 2, 2026
@vvv214 vvv214 force-pushed the codex/require-public-numeric-bounds branch 8 times, most recently from 52b0078 to 650a935 Compare July 2, 2026 17:35
@vvv214 vvv214 marked this pull request as ready for review July 2, 2026 17:35
@vvv214 vvv214 force-pushed the codex/require-public-numeric-bounds branch from 650a935 to e11d65c Compare July 14, 2026 05:53
Require pipeline numerical attributes to provide public NumericalAttribute bounds before DP quantile derivation instead of deriving exact min/max from sensitive data.
@vvv214 vvv214 force-pushed the codex/require-public-numeric-bounds branch from e11d65c to 84b1d45 Compare July 14, 2026 05: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.

1 participant