Repository navigation

Issues

Index state should be keyed by subspace key rather than by name
#514 · alecgrieser opened on Apr 4, 2019

Expressions over index columns and fields force a record fetch instead of a COVERING scan
Feature
FoundationDB/fdb-record-layer#4794 · opened on Oct 27, 2026
AvailableFields.ConditionalUponPathPredicate.fromProto rebuilds the ordinal path from the loop index
FoundationDB/fdb-record-layer#4791 · opened on Oct 26, 2026
CREATE STORED QUERY railroad diagram is too wide and gets clipped under the page's table of contents
Task
FoundationDB/fdb-record-layer#4790 · opened on Oct 26, 2026
RelationalStructFacadeBuilder.getZeroBasedOffset always returns -1, so overwriting a field adds a duplicate
FoundationDB/fdb-record-layer#4786 · opened on Oct 23, 2026
Stop writing zero_based_ordinality on explode plans and drop it from PRecordQueryExplodePlan
FoundationDB/fdb-record-layer#4769 · opened on Oct 21, 2026
Index-entry-to-record translation reads all nulls when a SQL identifier had to be escaped
Bug
FoundationDB/fdb-record-layer#4758 · opened on Oct 16, 2026
The planning cost model may choose ISCAN over a superior COVERING scan, depending on the order in which it compares the candidates
Task
FoundationDB/fdb-record-layer#4751 · opened on Oct 14, 2026
Add support for DATETIME and INTERVAL data types
FoundationDB/fdb-record-layer#4738 · opened on Oct 13, 2026
Merging struct types renumbers fields and drops the type name (for array literals, COALESCE)
FoundationDB/fdb-record-layer#4734 · opened on Oct 12, 2026
1
MetaDataProtoEditor record type renames can change indexes declared via the (field).index extension
Bug
FoundationDB/fdb-record-layer#4733 · opened on Oct 9, 2026
MetaDataProtoEditor record type renames can leave the canonical union field unrenamed
Bug
FoundationDB/fdb-record-layer#4732 · opened on Oct 9, 2026
Aggregates over an index on an unnested record type never use a covering scan
FoundationDB/fdb-record-layer#4720 · opened on Oct 7, 2026
Support renaming non-parent unnested constituents in MetaDataProtoEditor instead of rejecting them
Feature
FoundationDB/fdb-record-layer#4707 · opened on Oct 2, 2026
Change QueryCachingFlags.WITH_NO_CACHE_OPTION to Options.Name.NO_CACHE
FoundationDB/fdb-record-layer#4697 · opened on Oct 1, 2026
RankIndexMaintainer processes 0-based rank, SQL is 1-based
Task
FoundationDB/fdb-record-layer#4694 · opened on Sep 30, 2026
Drop the generated segment from proto package names in yaml-tests
FoundationDB/fdb-record-layer#4655 · opened on Sep 23, 2026
An unconstrained plan poisons its tertiary plan-cache entry, suppressing better plans for other literals
FoundationDB/fdb-record-layer#4642 · opened on Sep 18, 2026
ArithmeticValue always reports a nullable result type, even when both operands are not nullable
FoundationDB/fdb-record-layer#4622 · opened on Sep 15, 2026
Cost model scores a nested data access the same as an unnested one, so an IN-join can be chosen over a single scan
FoundationDB/fdb-record-layer#4621 · opened on Sep 15, 2026
Rethink IndexGenerationResult to account for not repeatedly create SyntheticTables that can be reused from the SchemaTemplate
FoundationDB/fdb-record-layer#4616 · opened on Sep 14, 2026
Support [NOT] IN (SELECT …) subqueries
Feature
FoundationDB/fdb-record-layer#4615 · opened on Sep 11, 2026
Derive ranks incrementally when scanning a rank index instead of one ranked-set probe per entry
Task
FoundationDB/fdb-record-layer#4608 · opened on Sep 10, 2026
Add more interesting kinds of validation to FDBClientKnobs
Feature
FoundationDB/fdb-record-layer#4607 · opened on Sep 10, 2026
Covering index scans cannot produce a partial record when a field is required (not nullable).
FoundationDB/fdb-record-layer#4592 · opened on Sep 8, 2026
1
The RecordConstructorValue composite accumulator may throw VerifyException when resuming a multi-aggregate group mid-way
Bug
FoundationDB/fdb-record-layer#4573 · opened on Sep 7, 2026
1