planned
partitioning
Scoping query execution to a subset of a collection by time range, region, or tenant — planned, not yet implemented.
| Subpath (reserved, not yet implemented) | @noy-db/hub/partitioning |
| Factory | none yet |
| Layer | not yet assigned |
Partitioning is a planned service that would let a query be scoped to a
subset of a collection — for example
only the last 30 days, only one region, or only one tenant — instead of
scanning every record. It does not exist yet: there is no with-partitioning
subsystem and no factory to opt in with. The only related public surface is
the JoinLeg.partitionScope type field described below, which the query
executor ignores today.
Current status
The query engine's join logic already carries a per-join-leg partitionScope
field internally, but every leg is always scoped to 'all' today — nothing
in the engine narrows execution by partition yet. This is internal plumbing,
not a public API: there is no way to opt into partition scoping from
application code.