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

A record-oriented store built on FoundationDB

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

If you have an ungrouped aggregate index (though I think this also works on a grouped aggregate index if your scan boundary aligns with the group), then when the aggregate...

bug

There are multiple yaml tests that are not run in force continuation mode (via annotation or `maxRows:0`). To increase coverage, we want to remove those exclusions.

* Problem: in aggregate queries, if a scan is stopped in the middle of a group, we'll just return the current result, which is wrong, and continuation = current row,...

bug fix

Forcing a continuation on a COALESCE query in mixed mode causes the query to fail Steps To Reproduce: 1. Look at functions.yamsql 2. Change the test to look like: 3....

bug

Currently, the nullability of the field is being checked and enforced in the record-core which is throwing a verify exception. We should probably catch it before.

enhancement

If we have a SQL statement like the following: ```sql select a & 1, a & 2 from t order by a & 1, a & 2 ``` The planner...

bug
planner

When a scan is stopped in the middle of a group, we just return the aggregation result. This is incorrect, and the if we continue with the returned continuation, the...

We are supposed to be including the `Built-Date` and `Built-By` in the manifest in our jars, but looking at the recent server-all jars, it is not included.

If multiple concurrent writes to different records come in (which is normally allowed), and the lucene IndexWriter hadn't already been initialized, the synchronized block can use up all the threads...