You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Michael Ho (JIRA)" <ji...@apache.org> on 2019/06/12 02:23:00 UTC

[jira] [Created] (IMPALA-8656) Support for eagerly fetching and spooling all query result rows

Michael Ho created IMPALA-8656:
----------------------------------

             Summary: Support for eagerly fetching and spooling all query result rows
                 Key: IMPALA-8656
                 URL: https://issues.apache.org/jira/browse/IMPALA-8656
             Project: IMPALA
          Issue Type: Improvement
          Components: Backend
    Affects Versions: Impala 3.2.0, Impala 2.12.0
            Reporter: Michael Ho


Impala's current interaction with clients is pulled-based: it relies on clients to fetch results to trigger the generation of more result row batches until all the result rows have been produced. If a client issues a query without fetching all the results, the query fragments will continue to consume the resources until the query hits is cancelled and unregistered for whatever reasons. This is undesirable as resources are held up by misbehaving clients and other queries may wait for extended period of time in admission control due to this.

The high level idea for this JIRA is for Impala to have a mode in which result sets of queries are eagerly fetched and spooled somewhere (preferably some persistent storage). In this way, the cluster's resources are freed up once all result rows have been fetched and stored in the spooling location. Incoming client fetches can be returned from this spooled locations.

cc'ing [~stakiar], [~twm378], [~joemcdonnell], [~lv]



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org