[ 
https://issues.apache.org/jira/browse/FLINK-7548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16221865#comment-16221865
 ] 

ASF GitHub Bot commented on FLINK-7548:
---------------------------------------

Github user fhueske commented on a diff in the pull request:

    https://github.com/apache/flink/pull/4894#discussion_r147339574
  
    --- Diff: 
flink-libraries/flink-table/src/main/scala/org/apache/flink/table/catalog/ExternalTableSourceUtil.scala
 ---
    @@ -124,9 +124,15 @@ object ExternalTableSourceUtil extends Logging {
               } else {
                 FlinkStatistic.UNKNOWN
               }
    +
               convertedTableSource match {
    -            case s : StreamTableSource[_] => new StreamTableSourceTable(s, 
flinkStatistic)
    -            case _ => new TableSourceTable(convertedTableSource, 
flinkStatistic)
    +            case s: StreamTableSource[_] =>
    --- End diff --
    
    In that case a `StreamTableSourceTable` is registered. I kept the previous 
behavior. 
    We can fix it in a follow up issue and make the decision based on the 
execution environment.


> Support watermark generation for TableSource
> --------------------------------------------
>
>                 Key: FLINK-7548
>                 URL: https://issues.apache.org/jira/browse/FLINK-7548
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API & SQL
>            Reporter: Jark Wu
>            Assignee: Fabian Hueske
>            Priority: Blocker
>             Fix For: 1.4.0
>
>
> As discussed in FLINK-7446, currently the TableSource only support to define 
> rowtime field, but not support to extract watermarks from the rowtime field. 
> We can provide a new interface called {{DefinedWatermark}}, which has two 
> methods {{getRowtimeAttribute}} (can only be an existing field) and 
> {{getWatermarkGenerator}}. The {{DefinedRowtimeAttribute}} will be marked 
> deprecated.
> How to support periodic and punctuated watermarks and support some built-in 
> strategies needs further discussion.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to