You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Paolo Castagna (JIRA)" <ji...@apache.org> on 2011/09/11 23:10:09 UTC
[jira] [Closed] (JENA-111) Improving TopN optimization in case of
an intermediate OpModifier
[ https://issues.apache.org/jira/browse/JENA-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paolo Castagna closed JENA-111.
-------------------------------
> Improving TopN optimization in case of an intermediate OpModifier
> -----------------------------------------------------------------
>
> Key: JENA-111
> URL: https://issues.apache.org/jira/browse/JENA-111
> Project: Jena
> Issue Type: Improvement
> Components: ARQ
> Reporter: Sara Magliacane
> Assignee: Paolo Castagna
> Priority: Minor
> Labels: arq, optimization
> Attachments: JENA-111_ARQ_r1165795.patch, 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: http://www.atlassian.com/software/jira