Hi, thanks for looking into this.
On 15/09/2022 17.44, Lorenz Buehmann wrote:
Fuseki with in-memory backend or TDB?
TDB2.
Which version?
4.3.2
How large is the dataset? Not that I see how this simple query with a
single join should lead to a timeout, but any numbers are usually
helpful.
It's around 10M triples
Did you try the query without defining the default graph but using a
graph pattern, i.e.
SELECT *
WHERE {
GRAPH <https://a.b.c> {<https://x.y.z> a ?t .
?t skos:prefLabel ?l }
}
I have 2 graphs in the original query with FROMs. When selecting one of
them into GRAPH clause, it worked once, but took few minutes. Other
tries result timeout.
And/or did you try to reorder the triple patterns? The query optimizer
should prefer the first one though anyways as it can make use of spo
index (if it would be TDB)
Switching rows doesn't help.
On 15.09.22 11:16, Mikael Pesonen wrote:
This returns one row fast, say :C1
SELECT *
FROM <https://a.b.c>
WHERE {
<https://x.y.z> a ?t .
#?t skos:prefLabel ?l
}
and this too:
SELECT *
FROM <https://a.b.c>
WHERE {
#<https://x.y.z> a ?t .
:C1 skos:prefLabel ?l
}
But this always hangs until timeout
SELECT *
FROM <https://a.b.c>
WHERE {
<https://x.y.z> a ?t .
?t skos:prefLabel ?l
}
What am I missing here? I'm using Fuseki web GUI. Thanks!
--
Lingsoft - 30 years of Leading Language Management
www.lingsoft.fi
Speech Applications - Language Management - Translation - Reader's and Writer's
Tools - Text Tools - E-books and M-books
Mikael Pesonen
System Engineer
e-mail: mikael.peso...@lingsoft.fi
Tel. +358 2 279 3300
Time zone: GMT+2
Helsinki Office
Eteläranta 10
FI-00130 Helsinki
FINLAND
Turku Office
Kauppiaskatu 5 A
FI-20100 Turku
FINLAND
