[
https://issues.apache.org/jira/browse/JENA-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820021#comment-13820021
]
Rob Vesse commented on JENA-587:
--------------------------------
Not sure if those compatibility tests will help. These are primarily around
ensuring that applying the distinct before the ordering doesn't change the
query semantics.
What I actually think needs to be done is that the logic in
{{TransformDistinctToReduced}} needs to change so rather than applying only
when a {{ORDER BY}} is also present it should apply only when an {{ORDER BY}}
is not present. Without the {{ORDER BY}} ARQ's join strategy should guarantee
that {{REDUCED}} is equivalent to {{DISTINCT}} for the majority of cases (I
think there will always be some queries where this is not the case)
> SELECT DISTINCT returns duplicate results
> -----------------------------------------
>
> Key: JENA-587
> URL: https://issues.apache.org/jira/browse/JENA-587
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 2.11.0
> Reporter: Veyriere
> Attachments: D.ttl, Q.rq, bug Jena2.11.0.zip, jena-587.zip
>
>
> SELECT DISTINCT returns duplicate results. Attaching a small quads dump and
> the query to reproduce with TDB
> Reproduced with Jena 2.11.0 and Jena 2.10.1 (was working with 2.7.4)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
