Thank you Ruslan,
I will revert back to OWLIM 5.0 b5123 using Sesame 2.6.5 where all things seems
fines (except the removeRepository, but I can live with it). I was just
confused as I made tons of query testing to realise what are performance strong
and weak queries and suddenly it had changed i
Hi Marek,
The new behaviour after we introduced the QueryJoinOptimizer is a
feature we were looking for and it took much time to be implemented and
stabilized in Sesame because in the beginning it was implemented like a
different query model node (SPARQLIntersection), then this node
disappear
Hi Sinan,
Which version of OWLIM is this? Our experience is that these kinds of errors
result from repository corruption (due to a bug in OWLIM or some
outage/interruption that left the repository in a bad state).
Any further information in that line would be very helpful.
Cheers,
Ivan
On Mon
Hi Nico,
As of OWLIM 5.0, we upgraded our Lucene version to 3.5 (it used to be the
quite dated 3.0). I can see the following note in the Lucene docs:
"As of Lucene version 3.1, this class implements the Word Break rules from the
Unicode Text Segmentation algorithm, as specified in Unicode Stand
Hello Ruslan,
Thanks for such an exhaustive answer! For now, we can just avoid using
those optional property path elements in our Sparql queries and convert
them to use unions instead - it seems to work properly for us and
shouldn't be very time-consuming. This is still just a workaround thoug
Hello,
We just received the new Owlim version yesterday and we no longer
experience this problem. Thanks for fixing this!
--
Best regards,
Krzysztof Sielski
Poznan Supercomputing and Networking Center
W dniu 2012-06-19 09:41, Barry Bishop pisze:
Hi Krzysztof,
Just wanted to let you know tha
Hi Krzysztof,
Just wanted to let you know that issue was indeed fixed and is available
in v5.1
Best,
barry
Barry Bishop
OWLIM Product Manager
Ontotext AD
Tel: +43 650 2000 237
email: barry.bis...@ontotext.com
skype: bazbishop
www.ontotext.com
On 29/05/12 10:19, Ivan Peikov wrote:
Hi Krzysz
Hi Nico,
I am not aware of any change in the tokenisation of literals during
Lucene indexing, but I will discuss with the developers and get back to you.
Best,
barry
Barry Bishop
OWLIM Product Manager
Ontotext AD
Tel: +43 650 2000 237
email: barry.bis...@ontotext.com
skype: bazbishop
www.onto