[
https://issues.apache.org/jira/browse/FLINK-14789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
godfrey he updated FLINK-14789:
-------------------------------
Description: Many tpc-ds queries have predicates on date, like {{d_date
between '1999-02-01' and (cast('1999-02-01' as date) + INTERVAL '60' day)}},
It's very useful to find a better plan if the planner knows the max/min values
of date. However, max/min in {{ColumnStats}} only support {{Number}} type
currently. This issue aims to extend max/min type from {{Number}} to
{{Comparable}}, and then {{Date}}, {{Time}}, {{Timestamp}} even {{String}}
could be supported. (was: Many tpc-ds queries have predicates on date, like
`d_date between '1999-02-01' and (cast('1999-02-01' as date) + INTERVAL '60'
day)`, It's very useful to find a better plan if the planner knows the max/min
values of date. However, max/min in {{ColumnStats}} only support {{Number}}
type currently. This issue aims to extend max/min type from {{Number}} to
{{Comparable}}, and then {{Date}}, {{Time}}, {{Timestamp}} even {{String}}
could be supported.)
> extends max/min type in ColumnStats from Number to Comparable
> -------------------------------------------------------------
>
> Key: FLINK-14789
> URL: https://issues.apache.org/jira/browse/FLINK-14789
> Project: Flink
> Issue Type: Sub-task
> Components: Table SQL / Planner
> Reporter: godfrey he
> Priority: Major
> Fix For: 1.10.0
>
>
> Many tpc-ds queries have predicates on date, like {{d_date between
> '1999-02-01' and (cast('1999-02-01' as date) + INTERVAL '60' day)}}, It's
> very useful to find a better plan if the planner knows the max/min values of
> date. However, max/min in {{ColumnStats}} only support {{Number}} type
> currently. This issue aims to extend max/min type from {{Number}} to
> {{Comparable}}, and then {{Date}}, {{Time}}, {{Timestamp}} even {{String}}
> could be supported.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)