-
Notifications
You must be signed in to change notification settings - Fork 103
Issues: FoundationDB/fdb-record-layer
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
More fine-grained control for multi-version testing
enhancement
New feature or request
relational
issues related to relational FDB
#3114
opened Feb 6, 2025 by
alecgrieser
Add verifications to
yaml-tests
that assert on planner metrics regressions
#3113
opened Feb 6, 2025 by
normen662
Infinite continuations: sum(*) returns alternating rows forever
#3096
opened Feb 4, 2025 by
ohadzeliger
MultiServerConnectionFactory does not use the provided initialConnection for the first call
#3094
opened Feb 4, 2025 by
ScottDugas
ExplainPlanVisitorTest.doNotEvaluateOutsideOfLimit fails with seed=-8583523306282810308
#3077
opened Jan 30, 2025 by
ScottDugas
Insert statement does not fully validate the column names with supplied values
#3069
opened Jan 28, 2025 by
g31pranjal
NOT NULL
on type other than ARRAY is not respected by fdb-relational
#3068
opened Jan 28, 2025 by
g31pranjal
More efficient execution of Recursive CTE plans
performance
Performance issues
planner
Related to the query planner
#3043
opened Jan 15, 2025 by
hatyo
Add verbosity-level option to SQL New feature or request
relational
issues related to relational FDB
EXPLAIN
enhancement
#3028
opened Jan 10, 2025 by
hatyo
Allow style configuration (color, test attributes) for the
PrettyExplainFormatter
#3018
opened Jan 8, 2025 by
normen662
Add proper testing for GML and DOT plan serialization.
planner
Related to the query planner
#3017
opened Jan 8, 2025 by
normen662
LuceneOptimizedFieldInfosFormat may write a value that is too large
#3005
opened Dec 16, 2024 by
ScottDugas
Missing optimization opportunity in NLJ planning
planner
Related to the query planner
#3000
opened Dec 12, 2024 by
hatyo
Incorrect NLJ plan due to index fetch
planner
Related to the query planner
#2997
opened Dec 9, 2024 by
hatyo
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.