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

Sahil Takiar resolved IMPALA-6894.
----------------------------------
    Fix Version/s: Impala 3.4.0
       Resolution: Fixed

> Use an internal representation of query states in ClientRequestState
> --------------------------------------------------------------------
>
>                 Key: IMPALA-6894
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6894
>             Project: IMPALA
>          Issue Type: Sub-task
>          Components: Backend
>            Reporter: Bikramjeet Vig
>            Assignee: Sahil Takiar
>            Priority: Major
>              Labels: query-lifecycle
>             Fix For: Impala 3.4.0
>
>
> Having an internal representation of states will be useful as we can 
> conveniently add/remove new states and develop logic around those eg. 
> [initialization, analysis complete, planning complete/queued, running] (set 
> the stage for IMPALA-2568 and its sub-tasks), [cancelled, exception etc] 
> (IMPALA-1262).
> We can easily convert it to client (HS2 and Beeswax) specific states and 
> ensure there are no client visible changes.



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

Reply via email to