You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/06/20 20:53:25 UTC
[jira] [Commented] (JENA-723) TopN optimization -- QueryIterTopN
behaves differently with java8
[ https://issues.apache.org/jira/browse/JENA-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14039182#comment-14039182 ]
ASF subversion and git services commented on JENA-723:
------------------------------------------------------
Commit 1604241 from [~andy.seaborne] in branch 'jena/trunk'
[ https://svn.apache.org/r1604241 ]
JENA-723 : Processing distinct must be done first
> TopN optimization -- QueryIterTopN behaves differently with java8
> -----------------------------------------------------------------
>
> Key: JENA-723
> URL: https://issues.apache.org/jira/browse/JENA-723
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 2.11.2
> Environment: java 8
> Reporter: Andy Seaborne
> Assignee: Andy Seaborne
>
> Behaviour has changed; testing/ARQ/Optimization/opt-top-10 illustrates this.
> TopN was buggy but happened to work with Java7 and before. Something in Java8 behaves differently (PriorityQuery? some sort of hash orderingso data is presented differently?)
--
This message was sent by Atlassian JIRA
(v6.2#6252)