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

Tim Armstrong resolved IMPALA-3902.
-----------------------------------
    Resolution: Fixed

Closing because it is now broadly usable for many use cases. There are some 
issues that might cause challenges for migration of complex workloads that I 
have moved to IMPALA-10486.

> Multi-threaded query execution
> ------------------------------
>
>                 Key: IMPALA-3902
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3902
>             Project: IMPALA
>          Issue Type: Epic
>          Components: Backend
>    Affects Versions: Impala 2.6.0
>            Reporter: Marcel Kinard
>            Assignee: Tim Armstrong
>            Priority: Minor
>              Labels: multithreading
>
> Currently, a single query fragment is run in a quasi-single threaded manner 
> on a node: the scanners are run in multiple threads, but all other operators 
> (joins, aggregation) are run in the main thread.
> The goal is to add multi-threaded execution on a single node by running 
> multiple fragment instances (each of which runs in a single thread).



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to