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

overzealous empty path detection? #1718

Open
pfps opened this issue Jan 20, 2025 · 0 comments
Open

overzealous empty path detection? #1718

pfps opened this issue Jan 20, 2025 · 0 comments

Comments

@pfps
Copy link

pfps commented Jan 20, 2025

The query https://qlever.cs.uni-freiburg.de/wikidata/1glIyB

SELECT DISTINCT * WHERE { 
<http://www.wikidata.org/entity/Q11629> 
( (<http://www.wikidata.org/prop/direct/P279> / ((<http://www.wikidata.org/prop/direct/P279>)*|(<http://www.wikidata.org/prop/direct/P31>)*))
| (<http://www.wikidata.org/prop/direct/P31> / ((<http://www.wikidata.org/prop/direct/P279>)*|(<http://www.wikidata.org/prop/direct/P31>)*)) )
?x1 }

causes

This query might have to evaluate the empty path, which is currently not supported. In file "/local/data-ssd/qlever/qlever-code/src/engine/TransitivePathImpl.h " at line 160

But the equivalent https://qlever.cs.uni-freiburg.de/wikidata/5D68x8

SELECT DISTINCT * WHERE { 
<http://www.wikidata.org/entity/Q11629> 
( (<http://www.wikidata.org/prop/direct/P279> / <http://www.wikidata.org/prop/direct/P279>*)
| (<http://www.wikidata.org/prop/direct/P279> / <http://www.wikidata.org/prop/direct/P31>*)
| (<http://www.wikidata.org/prop/direct/P31> / <http://www.wikidata.org/prop/direct/P279>*)
| (<http://www.wikidata.org/prop/direct/P31> / <http://www.wikidata.org/prop/direct/P31>*) )
?x1 }

works fine.

Why is the former a problem?

There quite a few queries like this in the paths section of the wdbench benchmark.

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

No branches or pull requests

1 participant