Mulgara Project: Issueshttps://code.mulgara.org/https://code.mulgara.org/favicon.ico?15861924492009-10-20T08:30:52ZMulgara Project
Redmine Mulgara - Bug #208 (New): Subqueries not supported via RESThttps://code.mulgara.org/issues/2082009-10-20T08:30:52ZEric Kobrin -ekobrin-mulgara@velocitude.com
<p>When making a TQL REST request containing subqueries, <code>StreamedSparqlJSONAnswer</code> throws an exception due to addBinding() not supporting @TransactionalAnswer@s.</p> Mulgara - Bug #204 (New): TQL Causing Mulgara to hang (regression from 2.0.9 to 2.1.3)https://code.mulgara.org/issues/2042009-09-16T23:13:52ZDragisa Krsmanovic -dkrsmanovic@plos.org
<p>This particular query <em>never</em> returns in Mulgara 2.1.3</p>
<p>In Mulgara 2.0.9 it, correctly, returns with no results under one minute.</p>
<p>Same database was used for testing.</p>
<pre>
select $art $oqltmp1_1 $score0 from <local:///topazproject#prefix>
where $art <rdf:type> <http://rdf.topazproject.org/RDF/Article> in <local:///topazproject#filter:graph=ri>
and $art <http://purl.org/dc/terms/bibliographicCitation> $oqltmp2_2 in <local:///topazproject#filter:graph=ri>
and $oqltmp2_2 <http://rdf.plos.org/RDF/hasEditorList> $oqltmp2_3 in <local:///topazproject#filter:graph=ri>
and $oqltmp2_4 <mulgara:prefix> <rdf:_> in <local:///topazproject#prefix>
and $oqltmp2_3 $oqltmp2_4 $oqltmp2_1 in <local:///topazproject#filter:graph=ri>
and $oqltmp2_1 <mulgara:search> $oqltmp2_7fs in <local:///topazproject#lucene>
and $oqltmp2_7fs <http://xmlns.com/foaf/0.1/name> '"niyaz ahmed"' in <local:///topazproject#lucene>
and $oqltmp2_7fs <mulgara:score> $score0 in <local:///topazproject#lucene>
and $art <http://prismstandard.org/namespaces/1.2/basic/eIssn> $oqltmp1_1 in <local:///topazproject#filter:graph=ri>;
</pre> Mulgara - Bug #199 (New): TQL Load data encodinghttps://code.mulgara.org/issues/1992009-09-06T14:14:16ZGregg -gar@foo.bar
<pre>
To see this, take any ascii file, save it in emacs with latin-1 encoding, try to load it, get the error message. Then save it as utf-8 and it loads fine.
Ideally one should be able to specify any input encoding, but at a minimum I would suggest support for any form of Unicode, the (16?) ISO Latin encodings, one or two of the standard Japanese encodings, maybe a Chinese and Russian (KOI-8?).
I'm not sure how one would specify this; it should probably be specified in an HTTP header. I looked at the "SPARQL 2":http://www.w3.org/TR/sparql-features/#sparql-update new features draft and the "SPARUL":http://www.w3.org/Submission/2008/SUBM-SPARQL-Update-20080715/ stuff but I don't see any mention of charset stuff.</pre> Mulgara - Bug #190 (New): tql swallows uri fragmentshttps://code.mulgara.org/issues/1902009-08-13T22:03:23ZPaula Gearon
<p>eg. In the following query result, the #all is missing<br /><pre>
itql> select $o from <local:///topazproject#grants> where $s $p $o
and $o <mulgara:is> <topaz:permissions#all>;
variables: {"o"}
cnt = 1
o
-------------------
<topaz:permissions>
</pre></p> Mulgara - Bug #188 (New): Zipped N3 files not recognized when loadinghttps://code.mulgara.org/issues/1882009-06-26T01:42:29ZPaula Gearon
<p>Loading a zipped N3 file successfully unzips the file, but doesn't recognize the extension as referring to an N3 file. As a result, the system falls back to the RDF/XML content handler, which naturally fails.</p>
<p>This should be fixable if the content handler starts looking for .n3.gz as well as .n3.</p> Mulgara - Feature #166 (New): XA1.1 String pool needs cachehttps://code.mulgara.org/issues/1662008-11-04T16:33:00ZPaula Gearon
<p>We need caching for the XA1.1 string pool. This may not be needed when memory mapping is implemented.</p> Mulgara - Bug #164 (New): Timer no longer workinghttps://code.mulgara.org/issues/1642008-11-04T15:32:47ZPaula Gearon
<p>The "set time on" command is no longer working, apparently since the Command interface was introduced.</p>
<p>This is to be implemented on the client side.</p> Mulgara - Bug #162 (New): Transactions involving transactional resolvers do not have snapshot iso...https://code.mulgara.org/issues/1622008-10-23T13:40:30Zronald -ronald@foo.bar
<p>See <a class="external" href="http://www.topazproject.org/trac/ticket/1036">http://www.topazproject.org/trac/ticket/1036</a> for the scenario. Because<br />resolvers are enlisted lazily, mulgara suffers from the same problem. But<br />attempting to always enlist all resolvers at the beginning of every transaction<br />may be quite expensive, and is also in the case of the distributed resolver<br />nearly impossible.</p>
<p>We may want to add a flag so users can choose whether they want this or not.</p> Mulgara - Feature #161 (New): Support recovery in distributed resolver's MultiXAResourcehttps://code.mulgara.org/issues/1612008-10-23T13:35:25Zronald -ronald@foo.bar
<p>Transactions are currently not remembered across restarts. We could possibly<br />store transactions and their states locally in a graph.</p> Mulgara - Feature #119 (New): URI/IRI deconflationhttps://code.mulgara.org/issues/1192008-05-17T23:08:38ZPaula Gearon
<p>Audit SPARQL to ensure that only valid IRIs are being used. This is mostly the case, as IRIs are a subset of URI.</p> Mulgara - Feature #111 (New): Transitive constraints not detectedhttps://code.mulgara.org/issues/1112008-05-17T22:23:41ZPaula Gearon
<p>RLog does not generate Transitive Constraints, though these are easy to detect.</p>
<p>Just look for the pattern of:<br /> (var <URI> var)</p>
<p>If 2 or more of these are found, then compare the first variable in each to the last variable of all the others. Once a match is found, then those two constraints potentially merge to form a transitive constraint.</p>
<p>The variable to be dropped must first be searched for in the rest of the constraint. If it doesn't exist anywhere else, then the potential merge may go ahead.</p> Mulgara - Feature #110 (New): Subtractions in ruleshttps://code.mulgara.org/issues/1102008-05-17T22:15:38ZPaula Gearon
<p>Krule currently does not parse subtractions. These are managed by the query engine, and are supplied by rlog. They need to be included, especially for excluding certain data types (such as literals when inserting into a subject location).</p> Mulgara - Bug #108 (New): Triggering constraints in Krulehttps://code.mulgara.org/issues/1082008-05-17T21:55:23ZPaula Gearon
<p>When Krule runs a rule, it triggers other rules that it affects the underlying constraints for. These triggered rules test if they should run by comparing the size of their resolution to the last time they were run, and proceeding if that size has changed.</p>
<p>This needs to become a 2 stage process. Rules should trigger constraints, and constraints should run the above test. If the size of a constraint resolution changes, then it triggers the rule that it belongs to.</p> Mulgara - Feature #23 (New): We must find a more descriptive way of expressing the cost of iterat...https://code.mulgara.org/issues/232006-09-26T11:08:34ZAndrae Muys -andrae@netymon.com
<pre>
<code class="html syntaxhl">An increasing number of resolvers (relational, federating, distributed) cannot provide a meaningful upper-bound to their row-count.
<span class="nt"><br/></span>
<span class="nt"><br/></span>
Also row-count assumes a uniform cost of iteration, when iteration (as opposed to resolution) entails network latency this is unrealistic.
<span class="nt"><br/></span>
<span class="nt"><br/></span>
How do we handle this? Do we need some sort of bogomips-like timing constant to provide a baseline for comparison? Can we use this to also provide selectivity data that would also improve our join performance?
</code></pre> Mulgara - Bug #8 (New): Temp directory managementhttps://code.mulgara.org/issues/82006-07-11T13:50:53Zbrian -brian@foo.bar
<pre>
<code class="html syntaxhl">A research group has reported seeing Kowari fill up temp directories and fall over. This was on Solaris, but it might be a more general problem to solve. Nothing to reproduce it yet, but I just wanted to capture the experience to potentially investigate this issue moving forward.
<span class="nt"><br/></span>
<span class="nt"><br/></span>
The usage pattern was one big load and then mostly queries with the occasional insert.
</code></pre>