[ https://issues.apache.org/jira/browse/FLINK-18731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jark Wu closed FLINK-18731. --------------------------- Resolution: Fixed Fixed in master (1.12.0): - 8c301ba850d2ddc11a59802e4b916a9dcd8b42d9 - 60906fa9c3217c4f36af2a9295ed9c19d5073606 > The monotonicity of UNIX_TIMESTAMP function is not correct > ---------------------------------------------------------- > > Key: FLINK-18731 > URL: https://issues.apache.org/jira/browse/FLINK-18731 > Project: Flink > Issue Type: Bug > Components: Table SQL / Planner > Reporter: godfrey he > Assignee: godfrey he > Priority: Major > Labels: pull-request-available > Fix For: 1.12.0 > > > Currently, the monotonicity of {{UNIX_TIMESTAMP}} function is always > {{INCREASING}}, actually, when it has empty function arguments > ({{UNIX_TIMESTAMP()}}, is equivalent to {{NOW()}}), its monotonicity is > INCREASING. otherwise its monotonicity should be NOT_MONOTONIC. (e.g. > UNIX_TIMESTAMP(string)) -- This message was sent by Atlassian Jira (v8.3.4#803005)