You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Dan Hecht (JIRA)" <ji...@apache.org> on 2018/03/26 23:03:00 UTC

[jira] [Resolved] (IMPALA-6614) ClientRequestState should use HS2 TOperationState states rather than Beeswax QueryState

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

Dan Hecht resolved IMPALA-6614.
-------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.13.0

> ClientRequestState should use HS2 TOperationState states rather than Beeswax QueryState
> ---------------------------------------------------------------------------------------
>
>                 Key: IMPALA-6614
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6614
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.11.0
>            Reporter: Dan Hecht
>            Assignee: Dan Hecht
>            Priority: Minor
>             Fix For: Impala 2.13.0
>
>
> As noted in IMPALA-1262, it'd be better if ClientRequestState used HS2 states rather than Beeswax states, since the HS2 states are a superset and have an explicit state for CANCELED.  The goal of this Jira is to migrate CRS to use the HS2 type (but not change the client visible behavior), to set things up for the future.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)