-
Notifications
You must be signed in to change notification settings - Fork 52
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
SERVICE
query ignores LIMIT
#1655
Comments
I've replicated the error with the following query on the olympics dataset:
Whats happening is, the Service puts a So the Service-endpoint in the query above basically computes the same incorrect result as the following nested query:
It somehow works (returns one row) when |
@UNEXENU Thanks a lot for the reply. The issue has indeed nothing to do with SERVICE. It happens exactly when there is a subquery with a single index scan and a LIMIT. A minimal dataset-independent example is:
|
The following query should return a single row, but it takes forever because the
SERVICE
query is executed without theLIMIT 1
.@UNEXENU and @joka921 Do you have an idea why that is the case?
https://qlever.cs.uni-freiburg.de/wikidata/RJCTro
The text was updated successfully, but these errors were encountered: