[jira] [Updated] (FLINK-18717) reuse MiniCluster in table integration test class ?

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-18717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-18717:
-----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor  (was: auto-deprioritized-major 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.


> reuse MiniCluster in table integration test class ? 
> ----------------------------------------------------
>
>                 Key: FLINK-18717
>                 URL: https://issues.apache.org/jira/browse/FLINK-18717
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Planner
>    Affects Versions: 1.11.0
>            Reporter: godfrey he
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> before 1.11, {{MiniCluster}} can be reused in each integration test class. (see TestStreamEnvironment#setAsContext) 
> In 1.11, after we correct the execution behavior of TableEnvironment, StreamTableEnvironment and BatchTableEnvironment (see [FLINK-16363|https://issues.apache.org/jira/browse/FLINK-16363], [FLINK-17126|https://issues.apache.org/jira/browse/FLINK-17126]), MiniCluster will be created for each test case even in same test class (see {{org.apache.flink.client.deployment.executors.LocalExecutor}}). It's better we can reuse {{MiniCluster}} like before. One approach is we provide a new kind of  MiniCluster factory (such as: SessionMiniClusterFactory) instead of using  {{PerJobMiniClusterFactory}}. WDYT ?
>   



--
This message was sent by Atlassian Jira
(v8.20.1#820001)