evitaDB 2026.2 introduces a new
filter constraint histogramHaving for slider-driven, per-histogram range
selection on references. We need to adapt evitaLab so the new constraint is
usable from the query editor and query builder.
What the new constraint does
histogramHaving(referenceName, histogramName, from, to, groupSelector?) is a
FilterConstraint usable inside userFilter. It narrows a reference histogram
to a [from, to] range (both ends inclusive) and optionally selects a single
group within a grouped reference via a single entityHaving(...) child.
referenceName — required classifier (the reference hosting the histogram)histogramName — optional; may be omitted when the reference hosts exactly
one histogram (empty string is normalised to null)from / to — at least one must be non-null; when both are non-null they
must share the same plain type and from <= togroupSelector — optional single EntityHaving child identifying the group
slot for grouped histograms
Inside userFilter it acts as a range carrier so the reference-histogram
baseline does not contract under its own slider handle. Outside userFilter
it behaves like the equivalent referenceHaving(...) rewrite.
Example:
userFilter(
histogramHaving(
"parameterValues", "basicUnitValue",
50, 120,
entityHaving(attributeEquals("code", "height"))
),
histogramHaving(
"parameterValues", "basicUnitValue",
90, 140,
entityHaving(attributeEquals("code", "weight"))
)
)
What needs to change in evitaLab
- Add
histogramHaving to the codemirror-lang-evitaql plugin
(auto-completion + documentation), following the
process documented here.
- Make sure the new plugin version is consumed by evitaLab.
- Ensure the query editor and any query-builder UI surface the new constraint
(including the optional histogramName and the optional single
entityHaving group selector child).
References
evitaDB 2026.2 introduces a new
filter constraint
histogramHavingfor slider-driven, per-histogram rangeselection on references. We need to adapt evitaLab so the new constraint is
usable from the query editor and query builder.
What the new constraint does
histogramHaving(referenceName, histogramName, from, to, groupSelector?)is aFilterConstraintusable insideuserFilter. It narrows a reference histogramto a
[from, to]range (both ends inclusive) and optionally selects a singlegroup within a grouped reference via a single
entityHaving(...)child.referenceName— required classifier (the reference hosting the histogram)histogramName— optional; may be omitted when the reference hosts exactlyone histogram (empty string is normalised to
null)from/to— at least one must be non-null; when both are non-null theymust share the same plain type and
from <= togroupSelector— optional singleEntityHavingchild identifying the groupslot for grouped histograms
Inside
userFilterit acts as a range carrier so the reference-histogrambaseline does not contract under its own slider handle. Outside
userFilterit behaves like the equivalent
referenceHaving(...)rewrite.Example:
What needs to change in evitaLab
histogramHavingto thecodemirror-lang-evitaqlplugin(auto-completion + documentation), following the
process documented here.
(including the optional
histogramNameand the optional singleentityHavinggroup selector child).References
feat: add histogramHaving filter constraint(854f7adb7a)
evita_query/.../filter/HistogramHaving.javasummary visualisation: Support for reference summary and histogram statistics #405