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

Pulling up a Value through Ordering is not entirely correct #1905

Closed
hatyo opened this issue Nov 9, 2022 · 0 comments · Fixed by #1906
Closed

Pulling up a Value through Ordering is not entirely correct #1905

hatyo opened this issue Nov 9, 2022 · 0 comments · Fixed by #1906
Assignees
@hatyo
Labels
planner Related to the query planner

Comments

@hatyo
Copy link
Contributor

hatyo commented Nov 9, 2022

When pulling up a Value through ordering, it is possible that we do not clean up dependency lineage (found through the transitive closure) correctly if we don't find a dependency target in the pulled up value.

This causes some plan partitions to misrepresent their order causing Cascades to fail to plan some queries due to not being able to satisfy their ordering requirement because of that.
@hatyo hatyo added the planner Related to the query planner label Nov 9, 2022
@hatyo hatyo self-assigned this Nov 9, 2022
@hatyo hatyo mentioned this issue Nov 9, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hatyo hatyo

Labels
planner Related to the query planner
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix pulling up Value through Ordering hatyo/fdb-record-layer
1 participant
@hatyo