incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paolo Castagna (JIRA)" <>
Subject [jira] [Commented] (JENA-111) Improving TopN optimization in case of an intermediate OpModifier
Date Wed, 07 Sep 2011 13:40:10 GMT


Paolo Castagna commented on JENA-111:

> 4 looks right. 

There must be something strange going on here. I added tests to to ensure
4) is applied correctly. The tests pass, however there are failures elsewhere in the ARQ test
suite (as Sara pointed out). I am going to share the patch.

> 3 is harder because DISTINCT interacts with projection.

Yep, I learned that by doing it... and I don't have a good idea at the moment. 

> Improving TopN optimization in case of an intermediate OpModifier
> -----------------------------------------------------------------
>                 Key: JENA-111
>                 URL:
>             Project: Jena
>          Issue Type: Improvement
>          Components: ARQ
>            Reporter: Sara Magliacane
>            Assignee: Paolo Castagna
>            Priority: Minor
>              Labels: arq, optimization
>         Attachments: topk_project.patch
> In the TopN optimization (Jena-89)  it would be useful to handle also the case in which
there are some other OpModifiers (I think they are the only category of Ops that can be in
that position in the tree) between Slice and Order By, for example OpProject:
> (slice _1
>   (project ?s ...
>     (order by <condition>
> -> 
> (project ?s ...
>   (top 1 <condition>

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message