Make L2Denorm an array encoding instead of a scalar function - #9138
Draft
connortsui20 wants to merge 1 commit into
Draft
Make L2Denorm an array encoding instead of a scalar function#9138connortsui20 wants to merge 1 commit into
connortsui20 wants to merge 1 commit into
Conversation
This was referenced Aug 2, 2026
`L2Denorm` was registered as a `ScalarFnVTable`, but it never behaved like one. Its constructor took an `ExecutionCtx` and scanned both children to enforce a unit-norm invariant, `L2Norm` read its stored norms instead of recomputing, `CosineSimilarity` and `InnerProduct` reached into its physical children, and the compressor scheme named it as a produced encoding. Those are all properties of a physical decomposition, not of an operation over arbitrary well-typed values. Moves it to `vortex-tensor/src/encodings/l2_denorm/` as a real `VTable` with two slots (`normalized`, `norms`). Structural validation runs on construction and on deserialization, `try_new` additionally scans for the exact unit-norm invariant, and `try_new_trusted` skips that scan for lossy normalized children whose stored norms stay authoritative. Neither constructor is `unsafe`, since violating the contract produces wrong answers rather than undefined behavior. The encoding keeps the `vortex.tensor.l2_denorm` array ID and the same two-field metadata message, so the wire format is unchanged. Slice and filter now push down into both children through `reduce_parent`. The generic `ScalarFnArray` filter rule only fired when at most one child was non-constant, which for this encoding was almost never. Also makes `L2DenormScheme` cascade its two children like `TemporalScheme` does, which lets both `HACK TO SUPPORT L2 DENORMALIZATION` special cases come out of `CascadingCompressor`. The scheme now competes on measured size like every other scheme. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XEo4wnqKfAf1QLJbdrz76j Signed-off-by: Claude <noreply@anthropic.com>
connortsui20
force-pushed
the
ct/l2-denorm-encoding
branch
from
August 2, 2026 18:03
80daa53 to
63e459b
Compare
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
2 participants
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.
Rationale for this change
(semi-related) Tracking Issue: #9129
Proposed idiom: encodings may hold invariants over their children, scalar functions may not. A scalar function is an operation over any well-typed input. An encoding owns a physical decomposition, so it gets
VTable::validateand its own constructors to enforce whatever has to hold between its children.FoR is the one edge case that comes to mind. Its child is an offset from the reference, which is an invariant, but nothing enforces it and
encoded + referencewould work as a plain scalar function over any integer column.L2Denormwas on the wrong side of the line. Its constructor took anExecutionCtxand scanned both children for the unit-norm invariant, whichScalarFnFactoryExtcannot express.L2Normreads its stored norms instead of recomputing,CosineSimilarityandInnerProductreach into its children,L2DenormSchemealready listed it inproduced_encodings, and persisting it needed aScalarFnArrayPluginbehind an env var.What changes are included in this PR?
L2Denormbecomes aVTableinvortex-tensor/src/encodings/l2_denorm/with slotsnormalizedandnorms.try_newscans for the exact invariants,try_new_trustedskips the scan for lossy normalized children. Neither isunsafe, since breaking the contract gives wrong answers rather than undefined behavior.ScalarFnArrayrule only fires when at most one child is non-constant.L2DenormSchemecascades its children likeTemporalScheme, which removes bothHACK TO SUPPORT L2 DENORMALIZATIONcases fromCascadingCompressor.What APIs are changed? Are there any user-facing changes?
scalar_fns::l2_denorm::*encodings::l2_denorm::*L2Denorm::try_new_array(n, s, ctx)L2Denorm::try_new(n, s, ctx)unsafe L2Denorm::new_array_unchecked(n, s)L2Denorm::try_new_trusted(n, s)L2Denorm::new()session.scalar_fns().register(L2Denorm)session.arrays().register(L2Denorm), unconditionalScalarFnArrayPlugin::new(L2Denorm)VX_SCALAR_FN_ARRAY_TENSOR_PLUGINno longer gatesL2Denorm, since the compressor can emit it. The array ID andL2DenormMetadataare unchanged, so the on-disk bytes match.L2DenormSchemestays out ofALL_SCHEMES.