[jira] [Created] (FLINK-13213) MinIdleStateRetentionTime/MaxIdleStateRetentionTime in TableConfig will be removed after call toAppendStream/toRetractStream without QueryConfig parameters

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (FLINK-13213) MinIdleStateRetentionTime/MaxIdleStateRetentionTime in TableConfig will be removed after call toAppendStream/toRetractStream without QueryConfig parameters

Shang Yuanchun (Jira)
Jing Zhang created FLINK-13213:
----------------------------------

             Summary: MinIdleStateRetentionTime/MaxIdleStateRetentionTime in TableConfig will be removed after call toAppendStream/toRetractStream without QueryConfig parameters
                 Key: FLINK-13213
                 URL: https://issues.apache.org/jira/browse/FLINK-13213
             Project: Flink
          Issue Type: Task
          Components: Table SQL / API
            Reporter: Jing Zhang
            Assignee: Jing Zhang


There are two `toAppendStream` method in `StreamTableEnvironment`:
1.  def toAppendStream[T: TypeInformation](table: Table): DataStream[T]
2.   def toAppendStream[T: TypeInformation](table: Table, queryConfig: StreamQueryConfig): DataStream[T]

After convert `Table` to `DataStream` by call the first method or toRetractStream, the MinIdleStateRetentionTime/MaxIdleStateRetentionTime in TableConfig will be removed.




--
This message was sent by Atlassian JIRA
(v7.6.14#76016)