QueryViolation

EQ / NE on field names an array operand, and the storage cannot compare a whole array.

A counting query (count, paged total) matches every record, and the entry does not allow expensive operators.

A cursor sort names field twice once the identity tie-breaker is appended.

A cursor sort has more than max fields once the identity tie-breaker is appended.

Two sort fields (field is the later one) are bound to the same physical field, so one of them sorts nothing.

An event projection that keeps payloads must keep their type, so each payload can be read.

A paged query asks for an EXACT total, and the entry counts only up to its bound. An expensive operation the entry disables, so it shares that code.

construct (e.g. query operator[CONTAINS]) is expensive, and the entry does not allow expensive operators.

The gateway requires every query to state its entry, and this one ran under UNSPECIFIED.

The filter (and HAVING) of a query has more nodes or values (subject) than the entry allows.

A FIRST / LAST metric inside an element, or on a model without an event time, names no orderBy.

FIRST / LAST need a single value per record, both for the value and for its ordering field.

An identity filter or a cursor (whose tie-breaker is the identity) on a model that defines no identity.

A cursor token that does not decode for this model and effective sort.

Which error a violation renders as.

field and other are independent arrays, and the storage cannot sort by both.

A PREVIOUS window steps along the date group on field, but the filter conditions the field where its range cannot be shifted: outside the top-level AND, or with a value that is not an instant.

A filter or sort compares a sensitive field whose raw value must not be compared.

An aggregation whose HAVING, metric sort or windows the core computes read more than max groups, dense fill rows included. Metered while the rows arrive, so it can fail after the response started streaming.

A size the entry bounds (subject: a list or aggregation limit, a page index, size, window or offset, a cursor size) is value, outside min..max; a null bound is open.

A sort names more fields than any storage supports.

The storage cannot run feature: it declares the feature unsupported, or its native language cannot express the query (a backend's native check). field is the field involved, when there is one.

A stream its store cannot resume (no keyset of its sort, so no positions) that names no limit: it would read a list's default number of rows and stop, which a reader takes for every match.

A date group or date difference names a field whose values do not store instants as a date or an epoch, so no backend can read them as instants.

An aggregation that names no sort found more than its limit groups. Its first limit groups in key order would be a cut nobody asked for: a top-N needs a sort, and every group needs a higher limit.

The field grants none of capabilities.

A filter value falls outside the field's declared domain; field is the name as the request wrote it.

A stable, machine-readable code; a contract: codes are added, never renamed.

The logical field the violation is about, or null for model-level violations.

What the binding error names: the absolute logical field (or "") for a model rule, a request part otherwise.

The error this violation is rejected with; the one place a violation is rendered.