I’m seeing the same behavior with nothing to note in the logs.
On a side note I did notice a small error in the help page for queries
stardog help query execute
The third query under “EXAMPLES” has the --reasoning flag after the database name
stardog query myDb --reasoning "select ?type where { <urn:an:individual> rdf:type ?type }"
which I believe should be before the database name
stardog query --reasoning myDb "select ?type where { <urn:an:individual> rdf:type ?type }"
No biggie but I thought id mention it.
I also tried the query by specifying a connection string instead of the database name but that did not work either
stardog query execute http://localhost:5820/test;reasoning=true "select ...."
cannata
(Phil Cannata)
March 13, 2018, 1:42pm
22
I assume this is a bug then, yes?
Someone from Stardog would have to confirm but I think that’s a reasonable assumption at this time.
cannata
(Phil Cannata)
March 14, 2018, 4:07pm
24
It appears that the --reasoning flag is not being recognized for the stardog query command.
I hope this is a bug and not intended.
I thought that this sounded familiar so I searched old posts and found this which includes a possible workaround.
Thank you! I used SPARQL Update to update my graph but I do not know how to use it with reasoning. Is there any way to enable it in SPARQL or any other way?
jess
(Jess Balint)
March 14, 2018, 9:08pm
26
We have verified this bug and created issue #4173 to track it’s status.
Jess
cannata
(Phil Cannata)
March 15, 2018, 2:29pm
27
Thanks Jess, is there a way for me to track this and know when it’s fixed?
jess
(Jess Balint)
March 15, 2018, 3:55pm
28
Hey Phil,
We publish the list of issues implemented in each release in the release notes . This particular issue is not scheduled to be fixed in the next release. Please consider the workaround mentioned in the thread that Zachary posted.
Jess