Work on the class loader problem (this ticket) and on changing over to Sesame 2.6.3.
https://sourceforge.net/apps/trac/bigdata/ticket/496 (Sesame 2.6.3)
Downloaded the onejar from sourceforge and generated new JARs from an SVN checkout using:
mvn -Dmaven.test.skip=true clean install
Update the classpath for Eclipse and updated the sesame version in build.properties.
Removed the overridden version of QueryResultUtil from our code base since http://www.openrdf.org/issues/browse/SES-853 (QueryResultUtil fails when solutions have too many bindings.) was fixed in openrdf 2.6.0.
http://sourceforge.net/apps/trac/bigdata/ticket/439 (Class loader problem)
Moved all SPARQL grammar files related files from org.openrdf.query.parser.sparql into com.bigdata.rdf.sail.sparql and imported those few files which were not already present (NegatedPropertySet, PropertySet, and UpdateExprBuilder) into the com.bigdata.rdf.sail.sparql package. Those files all represent features which we do not yet support (property paths and SPARQL 1.1 UPDATE). I will review their contents in depth when I work those issues.
Renamed the org.openrdf.query.parser.sparql.ast package to com.bigdata.rdf.sail.sparql.ast. This ensures that class path problems will not arise. Of course, it makes it more difficult to keep our version synchronized with the openrdf changes....
Recompiled the SPARQL grammar to fix errors created by the package name change. I needed to change the package name in many of the AST files and also in the sparql.jjt grammar. Quite a PITA.
TCK: 3 errors / 4 failures (6/8 if we run it as
TestBigdataSailWithQuads which runs the TCK twice).
sparql11-sum-02 : This is failing because openrdf still expects an
empty solution set rather than a single solution with a ZERO for the
sum. This is http://www.openrdf.org/issues/browse/SES-884
(Aggregation with an solution set as input should produce an empty
solution as output), which is clearly not fixed yet. Just checked
jira. They do not have a fix version for this yet.
Newly broken: None. All pre-existing tests which were passing are still passing.
The substr tests were known to be broken in openrdf 2.5.0.
The minus tests also reflected a problem with openrdf 2.5.0. I need to go back and look at them again to recall precisely what was failing.
There were at least two known problems with aggregation in 2.5.0 (see the links below, only one of which has been fixed. The issue which was fixed has to do with handling of type errors during aggregation and was demonstrated by sparql11-sum-03. See http://www.openrdf.org/issues/browse/SES-862 (Incorrect error handling for SPARQL aggregation; fix in 2.6.1)
New tests which are broken:
SPARQL 1.1 BINDINGS 01 (Failing on the BINDINGS clause.)
SPARQL 1.1 BINDINGS 02 (ditto)
sparql11-subquery-04 (Port into the AST TestTCK suite and debug there)
BSBM BI use case query 5 (This appears to be part of the Sesame TCK; fails with named solution set not found error)
Committed revision r6046.