fdb-record-layer
fdb-record-layer copied to clipboard
FoundationDB
A record-oriented store built on FoundationDB
For certain kinds of queries, the Cascades planner can construct IN-union and IN-join plans with non-sargable predicates. This means that the plans end up scanning over the same ranges multiple...
It is possible to have a `KeyExpression` whose key is referencing a complex type. For example: ``` [Field { 'A' None}/Field { 'B' None}, Field { 'A' None}/Field { 'C'...
The `MoreAsyncUtil` utility currently uses a statically defined `ScheduledThreadPoolExecutor` in order to schedule work efficiently. However, some users may want to have a little more control over how the executor...
As it seems: Synchronized runner is created by runner.startSynchronizedSessionAsync, while the calling runner sets itself as the underlying runner (which is the main runner for the indexing session). Let it...
This PR removes the Apache commons dependency from all of the non-test artifacts. It builds upon previous work that mostly removed our usage of the `Pair` class from that library,...
This PR enables planning aggregate rollups, it enables Cascades to choose aggregate indexes when planning queries with coarser groupings.
See comment https://github.com/FoundationDB/fdb-record-layer/pull/2899#discussion_r1753904755 This seems to be used there as a stand-in for null values: the associated implementations all look to return `null`. But I imagine it would be better...
### Example 1 We have an index on `15 - y`, it can be used for a query predicate `y < 10`! Something should turn `minus(15, y)` into `f(y)` and...
Metadata
Owner
Metadata
A record-oriented store built on FoundationDB