Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unable to construct a covering plan for a Lucene index over a Synthetic Record Type #1927

Closed
MMcM opened this issue Nov 18, 2022 · 0 comments · Fixed by #1928
Closed

Unable to construct a covering plan for a Lucene index over a Synthetic Record Type #1927

MMcM opened this issue Nov 18, 2022 · 0 comments · Fixed by #1928
Labels
planner Related to the query planner

Comments

@MMcM
Copy link
Contributor

MMcM commented Nov 18, 2022

No description provided.

@MMcM MMcM added the planner Related to the query planner label Nov 18, 2022
MMcM added a commit to MMcM/fdb-record-layer that referenced this issue Nov 18, 2022
@MMcM
Scott's test case for FoundationDB#1927: Unable to construct a coveri…
2e7d936 
…ng plan for a Lucene index over a Synthetic Record Type
@MMcM MMcM mentioned this issue Nov 18, 2022
Merged
MMcM added a commit that referenced this issue Nov 20, 2022
@MMcM
Fix covering plan for a Lucene index over a Synthetic Record Type (#1928
a952f05 
)

* Scott's test case for #1927: Unable to construct a covering plan for a Lucene index over a Synthetic Record Type

* Handle ListKeyExpression in primary key when pulling out Fetch.

* Handle nested Lucene functions for available fields.

* Clean up the test a little bit.

* trivial commit to rebuild.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
planner Related to the query planner
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix covering plan for a Lucene index over a Synthetic Record Type MMcM/fdb-record-layer
1 participant
@MMcM