Package-level declarations

How a Predicate.Compare compares. There is no NE; see Predicate.

How a query would be answered.

One index source of a plan, with what it would actually admit.

One index a plan used, and how far it reached at this snapshot.

A path a predicate is being written about.

What a query asks of a document.

What a query returns for each document it matches.

A predicate, what to return for each match, and how much of the store to look at.

The rows a query matched, in key order.

Answers queries against a store, using the indexes that exist and scanning what they do not cover.

What a query found and what it cost.

A literal a predicate compares against.

One result: a key, and whatever the projection asked for.

Every operand holds.

Every operand holds.

Both hold.

At least one operand holds.

One element at path satisfies operand, whose paths are relative to the element.

The same, from an expression: elemMatch("$.items[*]", …).

The operand does not hold, of the document. See Predicate for what that means at a path.

At least one operand holds.

Either holds.

The path, already parsed.

The path written as an expression, in the catalog's grammar: $.user.name, $.tags[*].

Every path this predicate mentions of the document, deduplicated, in the order first seen.