[
https://issues.apache.org/jira/browse/RYA-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329644#comment-15329644
]
David W. Lotts edited comment on RYA-71 at 6/14/16 3:25 PM:
------------------------------------------------------------
The original bug reporter reports ( 6/14/2016 10:30 AM ) that he has rebuilt
from the developement branch and still gets the same results. Bummer!
This may be the same bug: I just noticed this using the Vagrant example WAR.
It gives different response depending on the order of statements in the query:
{color:green}
prefix geonames: <http://www.geonames.org/ontology#>
SELECT ?f ?p ?o
WHERE {
?f a geonames:Feature .
?f ?p ?o .
}
{color}
== Successfully returns many results
== now change the order putting the all variable statement first:
{color:green}
SELECT ?f ?p ?o
WHERE {
?f ?p ?o .
?f a geonames:Feature .
}
{color}
== Results in this error:
{{Query evaluation error: org.openrdf.query.QueryEvaluationException:
mvm.rya.api.persist.RyaDAOException: java.lang.IllegalArgumentException:
TriplePattern[RyaStatement{subject=null, predicate=null, object=null,
context=null, qualifier=null, columnVisibility=null, value=null,
timestamp=1465916166369}] not supported }}
Inference is OFF.
All indexing is OFF.
was (Author: dlotts):
The original bug reporter reports ( 6/14/2016 10:30 AM ) that he has rebuilt
from the developement branch and still gets the same results. Bummer!
This may be the same bug: I just noticed this using the Vagrant example WAR.
It gives different response depending on the order of statements in the query:
```
prefix geonames: <http://www.geonames.org/ontology#>
SELECT ?f ?p ?o
WHERE {
?f a geonames:Feature .
?f ?p ?o .
}
```
Successfully returns many results
now change the order putting the all variable statement first:
```
SELECT ?f ?p ?o
WHERE {
?f ?p ?o .
?f a geonames:Feature .
}
### Results in this error:
Query evaluation error: org.openrdf.query.QueryEvaluationException:
mvm.rya.api.persist.RyaDAOException: java.lang.IllegalArgumentException:
TriplePattern[RyaStatement{subject=null, predicate=null, object=null,
context=null, qualifier=null, columnVisibility=null, value=null,
timestamp=1465916166369}] not supported
```
Inference is OFF.
All indexing is OFF.
> Order of statement patterns affects inference
> ---------------------------------------------
>
> Key: RYA-71
> URL: https://issues.apache.org/jira/browse/RYA-71
> Project: Rya
> Issue Type: Bug
> Components: sail
> Reporter: Puja Valiyil
> Assignee: David W. Lotts
>
> A user directly emailed me this bug:
> (Our testbed software configuration:
> web.rya 3.2.10-SNAPSHOT (This was from the master branch)
> accumulo 1.7.1
> zookeeper 3.4.8
> hadoop 2.6.4
> )
> The problem was found using a LUBM 1-University dataset (dataset attached):
> Query 1:
> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
> PREFIX ub: <http://swat.cse.lehigh.edu/onto/univ-bench.owl#>
> SELECT DISTINCT ?X
> WHERE
> { ?X rdf:type ub:Organization .
> ?X ub:subOrganizationOf <http://www.University0.edu>. }
> The result set is incorrect containing unrelated instances of type
> University. At the same time, the same query but with the order of statements
> switched (Query 2 below) returns correct results:
> Query 2:
> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
> PREFIX ub: <http://swat.cse.lehigh.edu/onto/univ-bench.owl#>
> SELECT DISTINCT ?X
> WHERE
> { ?X ub:subOrganizationOf <http://www.University0.edu>.
> ?X rdf:type ub:Organization . }
> Additionally, we have discovered a problem with the following query:
> Query 3:
> PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
> PREFIX ub: <http://swat.cse.lehigh.edu/onto/univ-bench.owl#>
> SELECT DISTINCT ?X ?Y
> WHERE
> { ?X ub:subOrganizationOf ?Y. ?Y rdf:type ub:University .
> ?X rdf:type ub:ResearchGroup . }
> This is similar to Query 1, but widens the query to all instances of type
> University. The query incorrectly returns 0.
> They also directly emailed me their data if you cannot recreate it easily.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)