UnpinnedEvents

Whether an events query that does not pin its aggregates runs: on a PostgreSQL or MongoDB log the indexes are the write store's and those of the access attributes, so a query that names no aggregateId scans the aggregate type's log, on the store the appends write to, unless an access policy's filter reads those. Such queries are a capability the log backends declare, so they run by default (ALLOW), bounded by the entry's budget, the store's QueryBulkhead and its read source; a deployment that wants none of them on its write store opts in to REFUSE, per store or per aggregate type (wow.query.events.unpinned, wow.stores.<name>.query.events.unpinned, wow.aggregates.[<context>.<aggregate>].query.events.unpinned).

Entries

Link copied to clipboard

The default: an events query may filter freely.

Link copied to clipboard

An events query must name its aggregates by aggregateId (an equality or IN, or ID, IDS, AGGREGATE_ID, AGGREGATE_IDS, among the conjuncts of its filter); any other is rejected STORAGE_UNSUPPORTED, and the model's descriptor lists the constraint AGGREGATE_REQUIRED.

Companion properties

Link copied to clipboard

Returns an immutable kotlin.enums.EnumEntries list containing the constants of this enum type, in the order they're declared.

Companion functions

Link copied to clipboard

Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)

Link copied to clipboard

Returns an array containing the constants of this enum type, in the order they're declared.