You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "John Fang (JIRA)" <ji...@apache.org> on 2018/06/06 03:52:00 UTC
[jira] [Commented] (CALCITE-2323) The configuration parameter
"defaultNullCollation" which enum NullCollation { LOW, HIGH, FIRST, LAST }
to allow alternative policies, but it can't take effect for over();
[ https://issues.apache.org/jira/browse/CALCITE-2323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16502797#comment-16502797 ]
John Fang commented on CALCITE-2323:
------------------------------------
[~julianhyde] can you help me review it again?
> The configuration parameter "defaultNullCollation" which enum NullCollation { LOW, HIGH, FIRST, LAST } to allow alternative policies, but it can't take effect for over();
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CALCITE-2323
> URL: https://issues.apache.org/jira/browse/CALCITE-2323
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: John Fang
> Assignee: Julian Hyde
> Priority: Major
>
> For example, the following query:
> *select deptno, rank() over(partition by empno order by deptno) from emp order by row_number() over(partition by empno order by deptno.*
> The default null order is nulls last for deptno in calcite. But the null order still is nulls last if we set the parameter "defaultNullCollation" with NullCollation.LOW.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)