Mulgara Project: Issueshttps://code.mulgara.org/https://code.mulgara.org/favicon.ico?15861924492009-02-03T05:55:09ZMulgara Project
Redmine Mulgara - Bug #180 (Closed): CONSTRUCT queries only handle 3 columnshttps://code.mulgara.org/issues/1802009-02-03T05:55:09ZPaula Gearon
<p>CONSTRUCT may work with any multiple of 3 elements, however Mulgara only handles a single set of 3.</p>
<p>e.g. The following query:<br /><pre>
construct { $s a ns:item; dc:text $o } where { $s ns:pred $o }
</pre><br />Gives an error of:<br /><pre>
cannot construct graph with 6 columns.
</pre></p> Mulgara - Bug #179 (Closed): Doing a FILTER REGEX with 2 parameters gives an errorhttps://code.mulgara.org/issues/1792009-02-03T05:44:42ZPaula Gearon
<p>Simple queries with 2 parameter regex filters fail with NPE. e.g.:<br /><pre>
select * where { ?s ?p ?o filter regex(?o, ".*sold.*") }
</pre></p>
<pre></pre> Mulgara - Bug #169 (Closed): CREATE on the SPARQL protocol should return RDF/XMLhttps://code.mulgara.org/issues/1692008-11-10T21:21:04ZPaula Gearon
<p>CREATE is basically being implemented as a select for 3 columns. That provides the correct data, but in the wrong format.</p>
<p>We need to use the RDF/XML exporter to convert the data being created into an RDF/XML graph.</p> Mulgara - Bug #157 (Closed): WebUI shouldn't need ; on TQLhttps://code.mulgara.org/issues/1572008-10-17T23:05:00ZPaula Gearon
<p>In the <a class="wiki-page" href="https://code.mulgara.org/projects/mulgara/wiki/WebUI">WebUI</a> every TQL command requires a ; character finishing it (or possibly a newline - I need to check). Also, newlines are not treated as whitespace.</p>
Before handing a query off to TQL we should check for the following:
<ul>
<li>If the text does not end in a ; then text to the end should be considered a query on its own.</li>
<li>newline characters should be replaced with spaces.</li>
</ul> Mulgara - Bug #156 (Closed): Translate rmi:// URIs into local URIshttps://code.mulgara.org/issues/1562008-10-17T22:27:27ZPaula Gearon
<p>URIs like:<br /> rmi://host/server#xxx<br />need to be sent to the server, and then have the relative "xxx" turned into the URI that gets used at the server end. Alternatively, the RMI server code should look for a "graph" parameter (ie. rmi://host/server?graph=foo:bar) that will be interpreted at the server end as an absolute URI.</p>
<p>This is dependent on <a class="issue tracker-3 status-27 priority-21 priority-default closed" title="Bug: Allow relative URIs in queries (Closed)" href="https://code.mulgara.org/issues/155">#155</a> due to the need to have both relative and absolute URIs.</p> Mulgara - Bug #152 (Closed): Exception on not-well-formed OPTIONAL querieshttps://code.mulgara.org/issues/1522008-10-15T21:15:54ZPaula Gearon
<p>The W3C test include the following:</p>
<pre><code>Nested-optionals with a shared variable that does not appear in<br /> the middle pattern (a not well-formed query pattern as per<br /> "Semantics and Complexity" of SPARQL</code></pre>
<p>The query is:<br /><pre>
PREFIX : <http://example/>
SELECT *
{
?X :name "paul"
{?Y :name "george" . OPTIONAL { ?X :email ?Z } }
}
</pre><br />There data is on the <a href="http://www.w3.org/2001/sw/DataAccess/tests/r2var-scope-join-1.ttl" class="external">W3C site</a></p>
<p>On running this query we get:<br /><pre>
org.mulgara.query.QueryException: Query failed
at org.mulgara.resolver.DatabaseSession.execute(DatabaseSession.java:754)
at org.mulgara.resolver.DatabaseSession.query(DatabaseSession.java:464)
at org.openrdf.sail.mulgara.MulgaraTripleSource.evaluate(MulgaraTripleSource.java:111)
at org.openrdf.sail.mulgara.MulgaraEvaluationStrategy.evaluate(MulgaraEvaluationStrategy.java:50)
... 27 more
Caused by: org.mulgara.query.MulgaraTransactionException: Transaction rollback triggered
at org.mulgara.resolver.MulgaraInternalTransaction.implicitRollback(MulgaraInternalTransaction.java:516)
at org.mulgara.resolver.MulgaraInternalTransaction.execute(MulgaraInternalTransaction.java:627)
at org.mulgara.resolver.DatabaseSession.execute(DatabaseSession.java:751)
... 30 more
Caused by: org.mulgara.query.QueryException: Failed to resolve constraintExpression
at org.mulgara.resolver.ConstraintOperations.resolveConstraintExpression(ConstraintOperations.java:197)
at org.mulgara.resolver.LocalQueryResolver.resolveE(LocalQueryResolver.java:269)
at org.mulgara.resolver.DatabaseOperationContext.doQuery(DatabaseOperationContext.java:786)
at org.mulgara.resolver.QueryOperation.execute(QueryOperation.java:139)
at org.mulgara.resolver.MulgaraInternalTransaction.execute(MulgaraInternalTransaction.java:623)
... 31 more
Caused by: org.mulgara.query.TuplesException: Bad [[LocalNode]] in constraint. constraint.getElement(0) returned a [[LocalNode]] with value: 0 constraint=[gn0 gn1449 gn1481 gn1369]
at org.mulgara.resolver.store.StatementStoreResolution.defineIndex(StatementStoreResolution.java:308)
at org.mulgara.resolver.store.StatementStoreResolution.<init>(StatementStoreResolution.java:156)
at org.mulgara.resolver.store.StatementStoreResolution.reresolve(StatementStoreResolution.java:371)
at org.mulgara.store.tuples.TuplesOperations.resolveNewlyBoundFreeNames(TuplesOperations.java:563)
at org.mulgara.store.tuples.TuplesOperations.unifyOperands(TuplesOperations.java:464)
at org.mulgara.store.tuples.TuplesOperations.join(TuplesOperations.java:244)
at org.mulgara.resolver.DefaultConstraintHandlers$5.resolve(DefaultConstraintHandlers.java:165)
at org.mulgara.resolver.ConstraintOperations.resolveConstraintExpression(ConstraintOperations.java:187)
... 35 more
</pre></p> Mulgara - Bug #150 (Closed): OPTIONAL not returning expected resultshttps://code.mulgara.org/issues/1502008-10-14T23:57:27ZPaula Gearon
<p>Unexpected results on an OPTIONAL clause. The toString on a query that demonstrates the problem is:<br /><pre>
SELECT $o1 $o2
FROM http://mulgara.org/local/server1#
WHERE ( optional ( optional ( and
[$s urn:test:pred1 $o1 $-anon-ctx1]
[$-anon-ctx1 rdf:type http://mulgara.org/mulgara#sailModel
http://mulgara.org/mulgara#sailModel]
) ( and
[$s urn:test:pred2 $o2 $-anon-ctx4]
[$-anon-ctx4 rdf:type http://mulgara.org/mulgara#sailModel
http://mulgara.org/mulgara#sailModel]
)
) ( and
[$s urn:test:pred2 $o2 $-anon-ctx7]
[$-anon-ctx7 rdf:type http://mulgara.org/mulgara#sailModel
http://mulgara.org/mulgara#sailModel]
[$s urn:test:pred3 $o1 $-anon-ctx10]
[$-anon-ctx10 rdf:type http://mulgara.org/mulgara#sailModel
http://mulgara.org/mulgara#sailModel]
)
) GIVEN 0 columns: (1 rows
)
</pre></p>
<p>The data is generated with:<br /><pre>
con.add(subj1, pred1, obj1);
con.add(subj1, pred2, obj2);
con.add(subj1, pred3, obj3);
</pre><br />The results we get are:<br /><pre>
var: $o2
tuples:
{$o2 $-anon-ctx10 $o1 $s $-anon-ctx7 (1 rows)
[000037 000032 000039 000033 000032 ]
}
</pre></p> Mulgara - Bug #120 (Closed): Repeated variables are not handled correctlyhttps://code.mulgara.org/issues/1202008-05-17T23:14:25ZPaula Gearon
<p>Basic graph patterns with repeated variables are not available in graphs defined with a variable.</p>
<p>Use the following mapping patterns (actual positions are variable):</p>
<p>($x $x * *) -> ($x $x1 * *) AND ($x1 $x * *)</p>
<p>($x $x $x *) -> ($x $x1 $x2 *) AND ($x2 $x $x1 *) AND ($x1 $x2 $x *)</p>
<p>($x $x $x $x) -> ($x $x1 $x2 $x3) AND ($x3 $x $x1 $x2) AND ($x2 $x3 $x $x1)</p> Mulgara - Bug #118 (Closed): SPARQL RegEx not complianthttps://code.mulgara.org/issues/1182008-05-17T23:07:05ZPaula Gearon
<p>Regular expressions are handled by Java and not an XPath compliant library.</p>
<p>Update Xalan and use the regex here.</p>
<p>Also consider adding xp: functions via reflection.</p> Mulgara - Bug #115 (Closed): Non-canonicalized dateTimeshttps://code.mulgara.org/issues/1152008-05-17T22:59:51ZPaula Gearon
<p>Literals of type xsd:dateTime are currently canonicalized to UTC.</p>
<p>These need to be stored with the timezone (so the original time can be restored), and with a flag to indicate if the original format was 00:00:00 or 24:00:00.</p>
<p>Timezones need only be stored in 15 minute increments.</p> Mulgara - Bug #99 (Closed): Variable graphs being ignoredhttps://code.mulgara.org/issues/992008-04-17T15:17:22ZPaula Gearon
<p>Selecting from an unbound graph is being ignored by all resolvers. This should not be ignored by the the XAResolver.</p>
<p>example:<br /><pre>
select $s $p $o $g from <rmi://localhost/server1#>
where $s $p $o $g;
</pre></p>
<pre>
logs:
<pre>
2008-04-17 09:55:20,647 WARN XSDResolver - Ignoring solutions for [$s $p $o $g]
2008-04-17 09:55:20,669 WARN [[PrefixResolver]] - Ignoring solutions for [$s $p $o $g]
2008-04-17 09:55:20,673 WARN [[LuceneResolver]] - Ignoring solutions for [$s $p $o $g]
</pre>
Also, prebinding the graph is also being ignored. This is a real issue as it does not allow for graph selection by property.
example:
<pre>
select $s $p $o $g from <rmi://localhost/server1#>
where $g <rdf:type> <mulgara:Model> and $s $p $o $g;
</pre>
*or*
<pre>
select $s $p $o $g from <rmi://localhost/server1#>
where $s $p $o $g and $g <rdf:type> <mulgara:Model>;
</pre>
<pre>
logs:
<pre>
2008-04-17 09:55:20,647 WARN XSDResolver - Ignoring solutions for [$s $p $o $g]
2008-04-17 09:55:20,669 WARN [[PrefixResolver]] - Ignoring solutions for [$s $p $o $g]
2008-04-17 09:55:20,673 WARN [[LuceneResolver]] - Ignoring solutions for [$s $p $o $g]
</pre></pre> Mulgara - Bug #97 (Closed): Language codes not implementedhttps://code.mulgara.org/issues/972008-04-15T18:41:24ZPaula Gearon
<p>Literals in the string pool are not encoded with language codes. In the past, this was put off "until later", but it is a serious lapse in supporting the RDF standards.</p>
<p>The places where literals are stored and retrieved from a byte buffer are:<br />The <strong>SPStringImpl</strong> class.<br /><strong>SPObjectFactoryImpl.newSPObject(Node)</strong> <em>this converts a <a class="wiki-page new" href="https://code.mulgara.org/projects/mulgara/wiki/LiteralImpl">LiteralImpl</a> into an SPStringImpl</em></p>
<p>I suggest using an escapable code for a separator character. This will allow minimal changes to the current system.</p> Mulgara - Bug #90 (Closed): Empty arguments in Krule descriptions can lead to NullPointerExceptionhttps://code.mulgara.org/issues/902008-03-21T20:04:10ZPaula Gearon
<p>A Krule Constraint argument of:<br /> <argument><br /> </argument><br />Causes a NPE. These arguments should be ignored at best, or a better exception at least.</p> Mulgara - Bug #67 (Closed): OOM on OSX using PowerPChttps://code.mulgara.org/issues/672007-07-16T17:38:21ZPaula Gearon
<pre>
<code class="html syntaxhl">Can get an OOM while running full set of scripted tests in OS X on a PPC architecture. The point of failure appears to vary.
<span class="nt"><br/></span>
<span class="nt"><br/></span>
While it appears that such failures are not critical, the reason for them should be tracked down, if possible.
</code></pre> Mulgara - Bug #7 (Closed): Xalan missing in Java 1.5https://code.mulgara.org/issues/72006-07-10T04:47:59ZPaula Gearon
<pre>
<code class="html syntaxhl">src/jar/descriptor/src/java/org/mulgara/descriptor/DescriptorElement.java uses classes from org.apache.xalan.templates.
<span class="nt"><br/></span>
This package was included in Java 1.4, but not in Java 1.5. The library needs to be brought in manually.
<span class="nt"><br/></span>
<span class="nt"><br/></span>
The bug does not show up on a Mac, as apple have included the package in the jar file:
<span class="nt"><br/></span>
/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Classes/.compatibility/14compatibility.jar
</code></pre>