le for sorting because SPARQL
allows for arbitrarily complex sort expressions, and the inputs to those
expressions may themselves be dynamically computed values that don’t exist
in the underlying dataset directly.
Rob
From: Chirag Ratra
Date: Tuesday, 19 March 2024 at 10:39
To: users@jena.apache.org , A
However, there is no indexing available for sorting because SPARQL
> allows for arbitrarily complex sort expressions, and the inputs to those
> expressions may themselves be dynamically computed values that don’t exist
> in the underlying dataset directly.
> >
> > Rob
>
to those expressions may
themselves be dynamically computed values that don’t exist in the underlying
dataset directly.
Rob
From: Chirag Ratra
Date: Tuesday, 19 March 2024 at 10:39
To: users@jena.apache.org , Andy Seaborne ,
dcchabg...@gmail.com
Subject: Re: [EXTERNAL] Re: Query Performance
@jena.apache.org , Andy Seaborne
, dcchabg...@gmail.com
Subject: Re: [EXTERNAL] Re: Query Performance Degrade With Sorting In Subquery
Is there any way to create an index or something?
On Tue, Mar 19, 2024 at 3:46 PM Rob @ DNR wrote:
> This is due to Jena’s lazy evaluation in its query eng
Is there any way to create an index or something?
On Tue, Mar 19, 2024 at 3:46 PM Rob @ DNR wrote:
> This is due to Jena’s lazy evaluation in its query engine.
>
> When you include a LIMIT clause on its own Jena only needs find the first
> N results (10 in your example) at which point it can
