Mike McMahon

`FDBNestedFieldQueryTest.nested2` explicitly creates an index with two adjacent copies of the same field. I do not think that there is any practical benefit to having such an index and that...

If rebuildIndex fails due to uniqueness violation, maybe mark disabled

1

Otherwise all of checkVersion will fail.

highlightTermsIn{Record,Message} is only called from tests

2

As of #2037.

For example, various kinds of `Point` queries for non-full-text fields, which might be combined with full-text searches and highlighting requested. I don't know whether these go into the map as...

Have indexing by record scan by key ranges instead of by tuple ranges

1

This avoids having to recover a `TupleRange` from an unbuilt `Range`. See https://github.com/FoundationDB/fdb-record-layer/pull/2651#discussion_r1559872782

Resolves #2801: Covering optimization with invertible index fields

5

This is complete for the heuristic planner. For Cascades, it adds the necessary partial record support, but more work in `tryFetchCoveringIndexScan` is needed, depending on how precisely function index keys...

Add more complete direction control to LogicalSortExpression.

10

Extends #2748 and #2771.

An `InvertibleFunctionKeyExpression` should be in `AvailableFields` in its original (inverted) form and inversion should be supported by `IndexKeyValueToPartialRecordTest`.