-
-
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 not working #280
Comments
With this the OpExecutor starts a Read transaction before executing the query. I leave the issue open since I would like to avoid the user indicating the graph to be queried (as for the queries without ondisk property). |
oh, for on ondisk you must do |
i tried to make ondisk behave just like in memory but it turned out that i almost opened an apache jena bug because i remember thinking it looks like it should be implemented. |
I tried to set the global property symUnionDefaultGraph as true as suggested here but didn't work. |
Closed via 6a1b0e1 |
Doesn't work when passing arguments in the BGP. |
Closed with 29b08b1 |
This query
gives
After inspecting the code I discovered that in the case of ondisk set, the query has to indicate the graph to be queried.
We can ignore for a moment that the query is supposed to give the same result with and without the ondisk set, but this
raises an exception
org.apache.jena.dboe.transaction.txn.TransactionException: Not in a transaction
.Probably, this is because the FacadeXOpExecutor doesn't start a READ transaction before executing the operation.
The text was updated successfully, but these errors were encountered: