Hi Alexandra,
If the repository is locked then this means it's being used by another
Java process.
One and the same BigOwlim image cannot be shared between different Java
processes.
If you are sure that no process is holding the image prior to starting
BigOwlim
then go to image's directory and
Hi John,
Failing to save the namespaces is a bug in Owlim-Lite and it has been
fixed in version 4.4 which will be available next week.
Cheers,
Ruslan
On 01/16/2012 11:10 AM, John Perdoni wrote:
Hi With regard to my post re namespaces disappearing, after further
investigation I have deduced
Hi Krzysztof,
As I am looking at the logs, it appears that all sizes of the triple
patterns were reported to be 0 which means missing or corrupted
predicate statistics (the 'predicate' file in the Owlim image is
probably 0 in size), i.e. corrupted repository. Because this happens
again, I con
ski
Poznan Supercomputing and Networking Center
W dniu 2012-05-21 18:09, Ruslan Velkov pisze:
Hi Krzysztof,
As I am looking at the logs, it appears that all sizes of the triple
patterns were reported to be 0 which means missing or corrupted
predicate statistics (the 'predicate' file i
etworking Center
W dniu 2012-05-22 18:21, Ruslan Velkov pisze:
Hi Krzysztof,
Thanks for the test code! We realised that we had some very trivial
problem when interpreting triple patterns which caused that
NullPointerException and it is now fixed. Predicate statistics are
also built correctly
Hi Krzysztof,
Many thanks for reporting this and for providing a test class!
What we introduced in 5.1 is the Sesame's QueryJoinOptimizer which
rearranges joins so that if there are sub-select clauses in the query
they will be evaluated first and in the best possible order (in terms of
number
ld ran faster?
Thank you for your time and looking forward for your response.
Best regards,
Marek
--------
*From:* Ruslan Velkov
*To:* owlim-discussion@ontotext.com
*Sent:* Monday, 18 June 2012, 15:53
*Subject:* Re: [Owlim-discuss
Hi Krzysztof,
Thanks again for sending a test case, they are really helpful for
quickly identifying the causes of the problems you experience!
The problem was in the way of calculating the collection size of a
triple pattern when the predicate is a wildcard (the calculation is done
different
Hi Krzysztof,
Thanks for raising this issue! The problem is in our implementation of
the Sesame's URI, BNode and Literal interfaces which hold the reference
to the pool that has created them (which we call the Entity pool) and
their internal ID with which these values are represented in the
r
Hi Erik,
Thanks for the observation!
Both Owlim-SE and Owlim-Lite used to implement the methods
addConnectionListener and removeConnectionListener since Sesame 2.0 but
a change in Sesame 2.2 made these methods belong to the then new
NotifyingSailConnection class. Because we kept using the ordi
Hi Jerven,
Thanks for reporting this!
This was part of our old policy for relaying part of the query
evaluation or the whole query evaluation to Sesame. Some time before we
did code cleanup to remove the usage of the RuntimeException in all
query-related classes, but obviously we have forgotte
Hi Ken,
This bug was due to incorrect setting of a flag and was fixed. It may
also appear in SELECT queries when specifying FROM clauses and
includeInferred is set to 'false' (additional statements from the
default graph will appear in the query result). The fix will be
available in the next
Hi Marek,
There is indeed a problem in the Sesame-Jena bridge (the SesameDataset
class) which prevents from normal usage of the named graphs. This will
be fixed for the next release. One way to work this around (although
this might be very inconvenient) is to use the Sesame interface to clear
Hi Jerven,
It appears that this issue has been fixed in a later revision. I'll send
you the 5.3 distribution with the fix in a separate email later today.
Cheers,
Ruslan
On 01/10/2013 11:25 AM, Jerven Bolleman wrote:
Hi Owlim devs,
I get the following error, please have a look into this.
T
Hi Krzysztof,
Sorry for the long delay!
The issue is Sesame-related and it has something to do with non-applying
DISTINCT operation on the result of the CONSTRUCT query, although
whether DISTINCT will be applied or not is implementation-dependent.
I can confirm that there is some strange beha
Hi Stefano,
We are sorry to hear that you experience problems!
We gave a try to reproduce this issue with synthetic data consisting of
1M statements and 100 owl:sameAs links between random entities,
performing thousands of small updates in the background of heavy
long-running queries and killi
Hi Nicola,
The sameAs optimization completes the transitive-symmetric closure of
the sameAs statements through backward chaining and converts all
statements into implicit ones during that process. So when exporting the
implicit graph you'll grab all the sameAs statements, including the root
i
into a graph, the equivalent instances are created
_within_ the same graph and not in the default graph as I expected. Is
that the expected behaviour or am I missing something?
Thanks,
Nicola
Il 17/04/2013 10:43, Ruslan Velkov ha scritto:
Hi Nicola,
The sameAs optimization completes the transitive
18 matches
Mail list logo
