[
https://issues.apache.org/jira/browse/CALCITE-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632689#comment-14632689
]
Julian Hyde commented on CALCITE-806:
-------------------------------------
Does that mean that it is illegal to use ROW_NUMBER with any other kind of
bound? Your change implies that
{code}ROW_NUMBER() OVER (ROWS BETWEEN 3 PRECEDING AND 2 FOLLOWING){code}
should be legal but would give the same result as
{code}ROW_NUMBER() OVER (){code}
Is that right?
Does your patch work under both JDK 1.7 and 1.8? I had to change my code
because the inherent non-determinism gave different results. You modified my
code and lost my later changes.
> ROW_NUMBER should emit distinct values
> --------------------------------------
>
> Key: CALCITE-806
> URL: https://issues.apache.org/jira/browse/CALCITE-806
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Fix For: next
>
>
> ROW_NUMBER should emit distinct values even for rows that have identical sort
> keys, or if there is no sort key. (This is distinct from RANK and DENSE_RANK,
> which emit the same value for rows with the same sort key.)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
