You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Rahul Challapalli (JIRA)" <ji...@apache.org> on 2017/05/09 23:56:04 UTC

[jira] [Created] (DRILL-5497) External sort's logic for memory allotment to each fragment should also consider width.max_per_query

Rahul Challapalli created DRILL-5497:
----------------------------------------

             Summary: External sort's logic for memory allotment to each fragment should also consider  width.max_per_query 
                 Key: DRILL-5497
                 URL: https://issues.apache.org/jira/browse/DRILL-5497
             Project: Apache Drill
          Issue Type: Bug
          Components: Execution - Relational Operators
    Affects Versions: 1.10.0
            Reporter: Rahul Challapalli
            Assignee: Paul Rogers


git.commit.id.abbrev=1e0a14c

Currently external sort only considers 'planner.width.max_per_node' option when computing the memory allocation to each fragment. It should also consider 'planner.width.max_per_query' as well. This allows users to externally control the desired parallelization for a query across the cluster.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)