[
https://issues.apache.org/jira/browse/JENA-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paolo Castagna updated JENA-111:
--------------------------------
Attachment: JENA-111_ARQ_r1165795.patch
I am sharing this patch (which is Sara's idea + a few tests) to let others see
the failing tests:
- ARQ - Scripts > Solution Sequence > Modifier OFFSET
- TS_DAWG > Approved > SPARQL Query Evaluation tests > Solution Sequence >
Offset 1
- TS_DAWG > Approved > SPARQL Query Evaluation tests > Solution Sequence >
Offset 2
(Ignore the 4 failures in TestOptimizer.java for now).
The three failures above are all very similar, for example:
Failure: Test 389 :: Modifier OFFSET
Query:
PREFIX : <http://example.org/ns#>
SELECT ?v
WHERE
{ _:b0 :str ?v }
ORDER BY ?v
OFFSET 2
Got: 0 --------------------------------
-----
| v |
=====
-----
Expected: 3 -----------------------------
---------
| v |
=========
| "1" |
| "AAA" |
| "aaa" |
---------
I don't understand what's going wrong here. :-/
> 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
