Repository navigation

We should have a way to define constraints on input and output schemas of a node #127

Open

Labels

enhancementirschema

opened

on Jul 10, 2026

If we have a L2/L3 node X, with input schema Y there can be restrictions on (a) what Y should be for a given X, and (b) output schema of X for a given input Y

For e.g., histogram_quantiles should only be able to operate on histogram type, not metrics types

milindsrivastava1997
changed the title ~~[-]schema definition of each node, input edge and output edge schema pairs have the constraints[/-]~~ [+]We should have a way to define constraints on input and output schemas of a node[/+] on Jul 10, 2026
zzylol
added
enhancementNew feature or request

irPre-ASAP or post-ASAP intermediate representation

schemaSchema, type, key, and nullability contracts
on Aug 26, 2026
zzylol commented on Aug 26, 2026
zzylol
on Aug 26, 2026
ContributorAuthor
Related open work

PromQL: agg intents should carry an explicit col, not implicit None for the value column #130 is a concrete ambiguous aggregate-column/schema contract.

Concat drops unique_keys unconditionally — no way for a producer to assert cross-branch disjointness #228 is a concrete unique-key propagation contract.

Extension registration in Add an explicit registration API for extending query/sketch/primitive/data types #131 must not bypass these schema/type constraints.
zzylol
added a parent issue on Oct 28, 2026
- Stage 0 review: frontends and the logical memo (hash-consed groups) #1011

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

Labels

enhancementirschema

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests