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

Kurt Young closed FLINK-14672.
------------------------------
    Fix Version/s: 1.10.0
       Resolution: Fixed

master: c4acb6fd287c27bd56d0898b69cf8fedd9cea788

> Make Executor stateful in sql client
> ------------------------------------
>
>                 Key: FLINK-14672
>                 URL: https://issues.apache.org/jira/browse/FLINK-14672
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / Client
>            Reporter: Kurt Young
>            Assignee: Zheng Hu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently sql client is stateless, it read config files into `Environment` 
> and recorded all session changes into `SessionContext`. 
> Each time sql client want to execute a new command, we have to first 
> construct `ExecutionContext` by combining `Environment` and `SessionContext`, 
> and then transfer all information into a new `EnvironmentInstance`. 
> It works well before but kind of hard to extend now. One example is support 
> creating table in sql client. We have to remember create statements and 
> replay them every time we want to execute a new command. 
> If we can make sql client stateful, and table environment be the state of sql 
> client, things will be much more easier. 
> This Jira should revisit all related classes, and define a clean relationship 
> between old roles after making sql client stateful. 
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to