[
https://issues.apache.org/jira/browse/IMPALA-7163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailesh Mukil resolved IMPALA-7163.
-----------------------------------
Resolution: Fixed
Fix Version/s: Impala 3.1.0
> Implement a state machine for the QueryState class
> --------------------------------------------------
>
> Key: IMPALA-7163
> URL: https://issues.apache.org/jira/browse/IMPALA-7163
> Project: IMPALA
> Issue Type: Sub-task
> Components: Distributed Exec
> Reporter: Sailesh Mukil
> Assignee: Sailesh Mukil
> Priority: Major
> Fix For: Impala 3.1.0
>
>
> We've recently been improving our query lifecycle by adding explicit state
> transitions so it's easier to reason about what should happen at a given
> stage in the lifetime of a query or a fragment instance.
> On the coordinator side. The coordinator's view of the query:
> https://github.com/apache/impala/commit/6ca87e46736a1e591ed7d7d5fee05b4b4d2fbb50
> On the fragment instance state side. A FIS's view of its own execution:
> https://github.com/apache/impala/blob/e12ee485cf4c77203b144c053ee167509cc39374/be/src/runtime/fragment-instance-state.h#L182-L203
> We don't have something like this for the QueryState class which maintains
> query wide state per executor. Adding it should make the lifecycle of a query
> from an executors point of view much easier to reason about.
> Additional info: This was identified as part of work for
> IMPALA-2990/IMPALA-4063, and is a precursor to it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
