[
https://issues.apache.org/jira/browse/FLINK-13213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-13213:
-----------------------------------
Labels: auto-unassigned pull-request-available stale-major (was:
auto-unassigned pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: New Feature
> Components: Table SQL / API
> Reporter: Jing Zhang
> Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)
