Hi all,
Thanks Øyvind, Lorenz, Rob for your hints, which were very helpful .
Most important was to reorder patterns in query and expand paths.
So that text:query pattern is at the top .
There is no difference when using subquery nor enclosing text:query pattern
into curly brackets.
You're right
triples for which you care about text
indexing) that just using a plain SPARQL 1.1 CONTAINS() filter expression is
sufficiently fast for these simple queries.
Rob
From: Goławski, Paweł
Date: Wednesday, 15 June 2022 at 14:38
To: users@jena.apache.org
Subject: Jena Full Text Search poor performance
Hi
Wouldn't it be already sufficient to move the pattern to the top of the
query? I thought Jena doesn't optimize custom property functions, i.e.
won't switch the order of those?
On 15.06.22 22:26, Øyvind Gjesdal wrote:
Hi Pawel,
I think this could be due to the text:query being evaluated late
Hi Pawel,
I think this could be due to the text:query being evaluated late in the
query, and other statements first computing many results, before the text
query limits it down. Maybe the contains filter gets applied earlier?
Would reordering the statements, expanding the property path and/or
Hi,
I'm trying to use Jena Full Text Search feature according to
https://jena.apache.org/documentation/query/text-query.html
I've noticed that queries using "text:query" are very slow: ~20 times slower
that similar using "FILTER contains" clause.
There are ~5.5M triples in database, 18230
