fdb-record-layer

fdb-record-layer copied to clipboard

Add `equals()` and `hashCode()` to `RecordQueryPlannerConfiguration`

3

hatyo

Performance profiling shows that the initialization of context file and format readers takes a long time during record updates. This optimization initializes the readers in a separate thread to reduce...

ohadzeliger

Attempting to Not Block on BlockTermsReader

2

Attempt to remove sequential blocking access during commit.

jleach4

We can shortcut the execution immediately when observing that one of the `PartialMatch`s has a remaining computation.

hatyo

When estimating the cardinality for an aggregate index plan, we check whether the equality-bound ordering values contain the grouping value(s), if so we estimate the cardinality to be either 0...

hatyo

Resolves #2108: Cascades should match record type key field with record type restrictions

5

This adds record type key matching to the Cascades planner. This is designed to handle two scenarios: 1. Record type key fields in an index. This makes some amount of...

alecgrieser

Index maintainer should be able to process index predicates

1

With #1997 we add support for sparse indexes, and enhance the index metadata with predicate information. With this PR, the index maintainer throws an exception if it encounters such an...

hatyo

The planner currently doesn't match reverse sorts correctly if there are some values bound with equality predicates. For example, if there is a query like: ```java RecordQuery.newBuilder() .setFilter(Query.field("a").equalsValue("foo")) .setSort(Key.Expressions.concatenateFields("a", "b"),...

alecgrieser

Store readable indexes bitset in `RecordStoreState`

2

hatyo

The Cascades planner currently doesn't match record type keys at all during planning. This can be a problem for operations like querying for a single type when the primary key...

alecgrieser