On 19/06/12 14:32, Simon Helsen wrote:
Hi guys,
I recently ran into a query which produced a surprising result and it is
not clear to me if I don't understand the spec correctly or whether it is
an ARQ bug. The scenario is that you have a quad store with e.g. 2
identical triples, except that the
Following up on my message from last week... After doing a little bit of
profiling, it turns out that the query execution time was dominated by
lookups to the TDB node table to translate between a NodeId (wrapper around
a long) and a Node (an RDF node). These lookups happen as a result of
calling A
[
https://issues.apache.org/jira/browse/JENA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396986#comment-13396986
]
Stephen Allen commented on JENA-261:
It is a little non-intuitive that SERVICE SILENT re
Ian Dickinson created JENA-263:
--
Summary: Adding resource property inside TDB transaction causes
message '*** UNEXPECTED'
Key: JENA-263
URL: https://issues.apache.org/jira/browse/JENA-263
Project: Ap
[
https://issues.apache.org/jira/browse/JENA-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ian Dickinson updated JENA-263:
---
Attachment: TdbTxText.java
Minimal test case to reproduce 'UNEXPECTED' error message on stdout
On 19/06/12 16:40, Simon Helsen wrote:
Right now, it just startling that in the span of a few weeks, a
serious performance regression got introduced and that it is not
understood.
The choice of language is yours.
On a side note: you seem to believe that 256 will be difficult to
fix.
I said
[
https://issues.apache.org/jira/browse/JENA-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne closed JENA-262.
--
> CacheFactory incorrectly uses hard-coded load factor
>
[
https://issues.apache.org/jira/browse/JENA-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396871#comment-13396871
]
Hudson commented on JENA-262:
-
Integrated in Jena_ARQ #661 (See [https://builds.apache.org/job/J
[
https://issues.apache.org/jira/browse/JENA-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-262.
Resolution: Fixed
Fix Version/s: ARQ 2.9.2
Assignee: Andy Seaborne
Doh.
Fixed in svn
Andy,
I was not suggesting to wait. That is a misunderstanding. I understand
that releasing often has benefits. I just hope that principle will also
apply once 256 is fixed (assuming it can be fixed). I.e. a quick release
especially if the performance regression was unnecessary.
On a side not
Alex Hall created JENA-262:
--
Summary: CacheFactory incorrectly uses hard-coded load factor
Key: JENA-262
URL: https://issues.apache.org/jira/browse/JENA-262
Project: Apache Jena
Issue Type: Bug
On 19/06/12 15:50, Simon Helsen wrote:
Andy,
I was basing that conclusion on the observations by Laurent. While I
understand that it is possible 0.9.0 had actual functional problems
(allowing it to be "faster"), the logic I am employing goes like this:
Release twice?
1) Laurent finds that 0.
Andy,
I was basing that conclusion on the observations by Laurent. While I
understand that it is possible 0.9.0 had actual functional problems
(allowing it to be "faster"), the logic I am employing goes like this:
1) Laurent finds that 0.9.0 is considerably faster than 0.9.1 release
2) I find t
Simon,
As someone who did not use 0.9.0, do you not think that we ought to move
cautiously?
Fixing the JENA-256 is a more major investigation and having fixed it
needs testing, if indeed, it is a regression rather than being more
careful, correctly, about the data - i.e. 0.9.0 may have been
[
https://issues.apache.org/jira/browse/JENA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396795#comment-13396795
]
Simon Helsen commented on JENA-260:
---
right, like the performance regression in JENA-256 (t
[
https://issues.apache.org/jira/browse/JENA-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396789#comment-13396789
]
Andy Seaborne commented on JENA-260:
I have put in a proper fix now (in TDB, inc. fixing
Hi guys,
I recently ran into a query which produced a surprising result and it is
not clear to me if I don't understand the spec correctly or whether it is
an ARQ bug. The scenario is that you have a quad store with e.g. 2
identical triples, except that they live in 2 separate graphs. So
if yo
[
https://issues.apache.org/jira/browse/JENA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396751#comment-13396751
]
Andy Seaborne commented on JENA-261:
The SERVICE SILENT is matching and returning a sing
[
https://issues.apache.org/jira/browse/JENA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396745#comment-13396745
]
Claude Warren commented on JENA-261:
Interestingly http://www.w3.org/TR/sparql11-query/#
[
https://issues.apache.org/jira/browse/JENA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne resolved JENA-261.
Resolution: Not A Problem
Resolving as "not a problem" because ARQ follows the SPARQL federate query
[
https://issues.apache.org/jira/browse/JENA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396694#comment-13396694
]
Andy Seaborne commented on JENA-261:
It's the UNION. Think of it as concatenate the res
[
https://issues.apache.org/jira/browse/JENA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396691#comment-13396691
]
Claude Warren commented on JENA-261:
Perhaps I have selected the wrong place to fix the
[
https://issues.apache.org/jira/browse/JENA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396680#comment-13396680
]
Andy Seaborne edited comment on JENA-261 at 6/19/12 11:21 AM:
--
[
https://issues.apache.org/jira/browse/JENA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396680#comment-13396680
]
Andy Seaborne edited comment on JENA-261 at 6/19/12 11:22 AM:
--
[
https://issues.apache.org/jira/browse/JENA-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396682#comment-13396682
]
Claude Warren commented on JENA-236:
After further research I don't theink the Silent, c
[
https://issues.apache.org/jira/browse/JENA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396680#comment-13396680
]
Andy Seaborne commented on JENA-261:
Claude:
The spec
http://www.w3.org/TR/sparql11-f
[
https://issues.apache.org/jira/browse/JENA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Warren updated JENA-261:
---
Attachment: JENA-261_patch.txt
Patch file that changes the QueryIterSingleton to a QueryIterNullIterato
[
https://issues.apache.org/jira/browse/JENA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396674#comment-13396674
]
Claude Warren commented on JENA-261:
The submitted patch works with my test data. There
Claude Warren created JENA-261:
--
Summary: QueryIterService returns an empty solution on exception
Key: JENA-261
URL: https://issues.apache.org/jira/browse/JENA-261
Project: Apache Jena
Issue Typ
Dear All
I am happy to announce the release of Elda 1.2.13 (Epimorphics' [1]
implementation of the Linked Data API [2]. Elda is available from
the downloads page [3] of http://elda.googlecode.com. Elda is
open source available by cloning its Mercurial repository [4].
The Linked Data API provides
30 matches
Mail list logo
