You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When executing the queries below with qlever, they are never solved and the error below is shown after 5 minutes. The same queries were tested with graphdb and they are solved in less than 2 seconds. You can replicate the issue with the following links:
For your information, I also tried to simplify the Query 2 by removing property paths, Values and filters but it still did not work (see query 3 below).
@tarcisiotmf The problem is that QLever's query planner currently generates all possible query plans (and then chooses the best). For large queries like yours, a heuristic is needed to limit the number of possible query plans that QLever evaluates.
It is on TODO list to do this automatically. Until then, you can easily do it manually by grouping parts of the query { ... }. Then for each such part, all query plans are generated and the best query plans for each part are combined. You should choose the groups, so that each group by itself makes sense by itself. The smaller the final result for each group, the better.
Please try it and let us know if it worked for you.
Thanks for the clarification! Currently, we are mostly evaluating available RDF stores for the different types of data and use cases we have at the SIB Swiss Institute of Bioinformatics including query examples in use (real-world applications).
Actually, the majority of our use cases involves queries that are indeed large. We also develop Question Answer (QA) systems over different independent SPARQL endpoints (with different RDF technologies). Then it would be significantly complex for us to handle case by case tailoring solutions to a specific RDF store by also considering that the queries are generated automatically by the QA system.
I am really impressed by the latest Qlever developments, once this issue is solved, it will be highly relevant for us.
When executing the queries below with qlever, they are never solved and the error below is shown after 5 minutes. The same queries were tested with graphdb and they are solved in less than 2 seconds. You can replicate the issue with the following links:
Executing query with qlever
Executing query with graphdb, select emi-dbgi repository
The dataset used in our test is available here.
For your information, I also tried to simplify the Query 2 by removing property paths, Values and filters but it still did not work (see query 3 below).
Query 1:
Query 2:
Query 3:
The text was updated successfully, but these errors were encountered: