[
https://issues.apache.org/jira/browse/FLINK-14882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328184#comment-17328184
]
Flink Jira Bot commented on FLINK-14882:
----------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Wrong null order when change flink default null order from NullCollation.LOW
> to NullCollation.FIRST
> ---------------------------------------------------------------------------------------------------
>
> Key: FLINK-14882
> URL: https://issues.apache.org/jira/browse/FLINK-14882
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 1.9.1
> Reporter: Leonard Xu
> Priority: Major
> Labels: stale-major
>
> Flink's default null collation keeps Nulls last for DESC, nulls first for ASC
> which named
> NullCollation.LOW. But when I change flink default null order from
> NullCollation.LOW to NullCollation.FIRST, the null order in SQL result do not
> change which not meet expected.
> change file: org.apache.flink.table.planner.calcite.FlinkPlannerImpl.scala
>
> cc [~danny0405]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
