[
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-deprioritized-major auto-deprioritized-minor auto-unassigned
pull-request-available (was: auto-deprioritized-major auto-unassigned
pull-request-available stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor,
> auto-unassigned, pull-request-available
> 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.20.10#820010)
