[
https://issues.apache.org/jira/browse/FLINK-12105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Mehra updated FLINK-12105:
--------------------------------
Description:
I ran into this while experimenting with different values at Lyft eng. However
it is reproducible with [https://github.com/ververica/sql-training] as well. I
showed this issue to the training instructors during flink-forward-19 and they
asked me to file this bug.
The INTERVAL values work fine until 99. Errors after that:
*TUMBLE(rideTime, INTERVAL '100' SECOND)*
_org.apache.calcite.sql.validate.SqlValidatorException: Interval field value
100 exceeds precision of SECOND(2) field_
*TUMBLE(rideTime, INTERVAL '100' MINUTE)*
_org.apache.calcite.sql.validate.SqlValidatorException: Interval field value
100 exceeds precision of MINUTE(2) field_
*TUMBLE(rideTime, INTERVAL '100' HOUR)*
_org.apache.calcite.sql.validate.SqlValidatorException: Interval field value
100 exceeds precision of HOUR(2) field_
*TUMBLE(rideTime, INTERVAL '100' DAY)*
_org.apache.calcite.sql.validate.SqlValidatorException:_ Interval field value
100 exceeds precision of DAY(2) field
(Note: MONTH AND YEAR also error out but for different reasons ("_Only constant
window intervals with millisecond resolution are supported_"). MONTH and YEAR
intervals are not supported at all currently. I was told that it is hard to
implement because of timezone differences. I will file that separately.)_
_
was:
I ran into this while experimenting with different values at Lyft eng. However
it is reproducible with [https://github.com/ververica/sql-training] as well. I
showed this issue to the training instructors during flink-forward-19 and they
asked me to file this bug.
The INTERVAL values work fine until 99. Errors after that:
*TUMBLE(rideTime, INTERVAL '100' SECOND)*
_org.apache.calcite.sql.validate.SqlValidatorException: Interval field value
100 exceeds precision of SECOND(2) field_
*TUMBLE(rideTime, INTERVAL '100' MINUTE)*
_org.apache.calcite.sql.validate.SqlValidatorException: Interval field value
100 exceeds precision of MINUTE(2) field_
*TUMBLE(rideTime, INTERVAL '100' HOUR)*
_org.apache.calcite.sql.validate.SqlValidatorException: Interval field value
100 exceeds precision of HOUR(2) field_
*TUMBLE(rideTime, INTERVAL '100' DAY)*
Interval field value 100 exceeds precision of DAY(2) field
(Note: MONTH AND YEAR also error out but for different reasons ("_Only constant
window intervals with millisecond resolution are supported_"). MONTH and YEAR
intervals are not supported at all currently. I was told that it is hard to
implement because of timezone differences. I will file that separately.)_
_
> TUMBLE INTERVAL value errors out for 100 or more value
> ------------------------------------------------------
>
> Key: FLINK-12105
> URL: https://issues.apache.org/jira/browse/FLINK-12105
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Client
> Affects Versions: 1.7.2
> Environment: [https://github.com/ververica/sql-training]
> Reporter: Vinod Mehra
> Priority: Major
>
> I ran into this while experimenting with different values at Lyft eng.
> However it is reproducible with [https://github.com/ververica/sql-training]
> as well. I showed this issue to the training instructors during
> flink-forward-19 and they asked me to file this bug.
> The INTERVAL values work fine until 99. Errors after that:
> *TUMBLE(rideTime, INTERVAL '100' SECOND)*
> _org.apache.calcite.sql.validate.SqlValidatorException: Interval field value
> 100 exceeds precision of SECOND(2) field_
> *TUMBLE(rideTime, INTERVAL '100' MINUTE)*
> _org.apache.calcite.sql.validate.SqlValidatorException: Interval field value
> 100 exceeds precision of MINUTE(2) field_
> *TUMBLE(rideTime, INTERVAL '100' HOUR)*
> _org.apache.calcite.sql.validate.SqlValidatorException: Interval field value
> 100 exceeds precision of HOUR(2) field_
> *TUMBLE(rideTime, INTERVAL '100' DAY)*
> _org.apache.calcite.sql.validate.SqlValidatorException:_ Interval field value
> 100 exceeds precision of DAY(2) field
> (Note: MONTH AND YEAR also error out but for different reasons ("_Only
> constant window intervals with millisecond resolution are supported_"). MONTH
> and YEAR intervals are not supported at all currently. I was told that it is
> hard to implement because of timezone differences. I will file that
> separately.)_
> _
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
