[
https://issues.apache.org/jira/browse/FLINK-14882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonard Xu updated FLINK-14882:
-------------------------------
Description:
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]
was:
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
which not meet expected.
change file: org.apache.flink.table.planner.calcite.FlinkPlannerImpl.scala
cc [~danny0405]
> 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
>
> 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)
