fdb-record-layer icon indicating copy to clipboard operation
fdb-record-layer copied to clipboard

A record-oriented store built on FoundationDB

Results 304 fdb-record-layer issues
Sort by recently updated
recently updated
newest added

IndexMaintainerRegistryImpl can only be initialized once because it uses a static instance. This can create problems during testing. This change adds a reset method that re-initializes the registry.

The main record store and index maintainers now clear out uncommitted version mutations when performing a record range delete. Previously, this failure to do so meant that it would be...

Versionstamp-related mutations are currently stored in a buffer in the JVM and flushed during commit. This is to support multiple updates to the same record happening during a single transaction....

bug

Currently the `UPDATE` plan only shows the source and where clause without depicting the set clauses, this information is necessary and can be useful sometimes when debugging.

enhancement
planner

This should be the first step toward deleting this module and its tests altogether.

I am facing a peculiar case when I run a query which uses Enum in querycomponent and also use sorting when I use enum in query but do not use...

Instead of doing block based storedFields, we should support key based storedFields to optimize the read amplification from FoundationDB.

This introduces `ReplaceValue` which performs transformations on an underlying `Value`.

Goal would be for readblock to produce not just the file it is reading but the reference inside the file it is attempting to read after the slice.