-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
ondisk and slicing #295
Comments
Actually, slicing and ondisk don't work as expected. The query
gives
instead of
|
what if you add |
Yes, I can get the bindings by adding the graph variable, but I would avoid this, otherwise the same query (without the graph) would give different results with ondisk. |
I close this issue as it is completed via f1355c0 |
…on before clearing the dataset
Enabling slicing with ondisk makes the engine open too many files (a new TDB is created for each slice) and the execution fails.
I'm not sure how to solve this. Maybe, we could just document this behaviour and suggest setting ondisk.reuse as "true" in case of sliced execution.
Alternatively, we could enforce by default ondisk.reuse=true when slicing is true.
The text was updated successfully, but these errors were encountered: