[
https://issues.apache.org/jira/browse/FLINK-14882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-14882:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or 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: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> 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.20.1#820001)
