[jira] [Commented] (FLINK-16584) Whether to support the long type field in table planner when the source is kafka and event time field's type is long
[ https://issues.apache.org/jira/browse/FLINK-16584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17319426#comment-17319426 ] Kurt Young commented on FLINK-16584: with 1.13, you can convert Long to TIMESTAMP_LTZ with builtin function TO_TIMESTAMP_LTZ. This type has builtin support with conversion between Long. I think it's enough to meet this requirement and I would close this issue. > Whether to support the long type field in table planner when the source is > kafka and event time field's type is long > - > > Key: FLINK-16584 > URL: https://issues.apache.org/jira/browse/FLINK-16584 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Reporter: hehuiyuan >Priority: Minor > > For rowtime function , the field type may be long or timestamp . > But the event time field type is only timestamp when use kafka connect. > Some validations (for example ,when create kafka table source ) are not > allowed long. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLINK-16584) Whether to support the long type field in table planner when the source is kafka and event time field's type is long
[ https://issues.apache.org/jira/browse/FLINK-16584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17180213#comment-17180213 ] Jark Wu commented on FLINK-16584: - Maybe TO_TIMESTAMP, see FLINK-16889 > Whether to support the long type field in table planner when the source is > kafka and event time field's type is long > - > > Key: FLINK-16584 > URL: https://issues.apache.org/jira/browse/FLINK-16584 > Project: Flink > Issue Type: Wish > Components: Table SQL / API >Reporter: hehuiyuan >Priority: Minor > > For rowtime function , the field type may be long or timestamp . > But the event time field type is only timestamp when use kafka connect. > Some validations (for example ,when create kafka table source ) are not > allowed long. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLINK-16584) Whether to support the long type field in table planner when the source is kafka and event time field's type is long
[ https://issues.apache.org/jira/browse/FLINK-16584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179336#comment-17179336 ] hehuiyuan commented on FLINK-16584: --- Hi [~jark] , what is the name of this function? > Whether to support the long type field in table planner when the source is > kafka and event time field's type is long > - > > Key: FLINK-16584 > URL: https://issues.apache.org/jira/browse/FLINK-16584 > Project: Flink > Issue Type: Wish > Components: Table SQL / API >Reporter: hehuiyuan >Priority: Minor > > For rowtime function , the field type may be long or timestamp . > But the event time field type is only timestamp when use kafka connect. > Some validations (for example ,when create kafka table source ) are not > allowed long. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLINK-16584) Whether to support the long type field in table planner when the source is kafka and event time field's type is long
[ https://issues.apache.org/jira/browse/FLINK-16584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17179334#comment-17179334 ] hehuiyuan commented on FLINK-16584: --- Hi [~jark] , what is the name of this function? > Whether to support the long type field in table planner when the source is > kafka and event time field's type is long > - > > Key: FLINK-16584 > URL: https://issues.apache.org/jira/browse/FLINK-16584 > Project: Flink > Issue Type: Wish > Components: Table SQL / API >Reporter: hehuiyuan >Priority: Minor > > For rowtime function , the field type may be long or timestamp . > But the event time field type is only timestamp when use kafka connect. > Some validations (for example ,when create kafka table source ) are not > allowed long. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLINK-16584) Whether to support the long type field in table planner when the source is kafka and event time field's type is long
[ https://issues.apache.org/jira/browse/FLINK-16584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058501#comment-17058501 ] Jark Wu commented on FLINK-16584: - We are planning to provide some built-in function to convert BIGINT into TIMESTAMP. > Whether to support the long type field in table planner when the source is > kafka and event time field's type is long > - > > Key: FLINK-16584 > URL: https://issues.apache.org/jira/browse/FLINK-16584 > Project: Flink > Issue Type: Wish > Components: Table SQL / API >Reporter: hehuiyuan >Priority: Minor > > For rowtime function , the field type may be long or timestamp . > But the event time field type is only timestamp when use kafka connect. > Some validations (for example ,when create kafka table source ) are not > allowed long. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
