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

Identify bugs and/or limitations with the provided SPJ query engine #21

Open
yunpengn opened this issue Mar 30, 2019 · 3 comments
Open

Identify bugs and/or limitations with the provided SPJ query engine #21

yunpengn opened this issue Mar 30, 2019 · 3 comments
Labels
bug Something isn't working

Comments

@yunpengn
Copy link
Owner

In this thread, we keep track of all bugs and/or limitations found in the provided SPI query engine.

Notice: here we keep track of the problems with the original codebase. We should consider the state of the codebase when we have not made any modifications to it.
@yunpengn yunpengn added the bug Something isn't working label Mar 30, 2019
@yunpengn
Copy link
Owner Author

The current optimiser only supports inner join. Its correctness is not guaranteed on outer joins, anti-joins and semi-joins, etc.

@yunpengn
Copy link
Owner Author

The current implementation of Join operator only supports 1 join column.

@yunpengn
Copy link
Owner Author

yunpengn commented Apr 3, 2019 •
edited
Loading

Bug in PlanCost, fixed by a381e72

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yunpengn