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.

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

CONSTRUCT with UNIONs fails #1681

Closed
ktk opened this issue Dec 15, 2024 · 2 comments · Fixed by #1682
Closed

CONSTRUCT with UNIONs fails #1681

ktk opened this issue Dec 15, 2024 · 2 comments · Fixed by #1682

Comments

@ktk
Copy link

ktk commented Dec 15, 2024

Query: https://qlever.cs.uni-freiburg.de/lindas/2hYcNK

Error: Assertion !subset.empty() && subset.back() < numColumns() failed. Please report this to the developers. In file "/local/data-ssd/qlever/qlever-code/src/engine/idTable/IdTable.h " at line 567

@ktk
Copy link
Author

ktk commented Dec 15, 2024

It works like this: https://qlever.cs.uni-freiburg.de/lindas/5tQs8K

@hannahbast
Copy link
Member

@ktk Thanks for reporting this! What's even weirder is that with the second query (that works) in the cache, the first query also works. We will investigate!

hannahbast pushed a commit that referenced this issue Dec 16, 2024
There was a bug in the following scenario: a UNION that is lazily computed and at least one of the inputs of the UNION contains a subquery that does not SELECT all possible variables. Then the UNION threw an assertion, because there was some confusion between the number of visible variables in the input (only the ones selected by the subquery) and the actual number of columns in the result (which includes the not-selected variables of the subquery).

Fixes #1681
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants