[
https://issues.apache.org/jira/browse/HIVE-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563438#comment-13563438
]
Phabricator commented on HIVE-3946:
-----------------------------------
navis has commented on the revision "HIVE-3946 [jira] Make it possible to
configure for each stage".
INLINE COMMENTS
ql/src/java/org/apache/hadoop/hive/ql/Driver.java:1351 ok.
ql/src/test/queries/clientpositive/config_per_stage.q:1 We are thinking of
using this for the managed query of which plan and configuration is stored with
it (and check plan before execution). If it's not, plan changes by optimization
would make it invalid as you stated.
Would it be possible to support this by providing generic expressions or
hint? It seemed hard and might be inaccurate.
ql/src/test/queries/clientpositive/config_per_stage.q:4 I cannot understand
this. Why stage-2 should be overridden by defaults? stage-1 will be run with 2
reducer and stage-2 will be run by 3 reducer regardless of adding one more
stage.
REVISION DETAIL
https://reviews.facebook.net/D8181
To: JIRA, navis
Cc: njain
> Make it possible to configure for each stage
> --------------------------------------------
>
> Key: HIVE-3946
> URL: https://issues.apache.org/jira/browse/HIVE-3946
> Project: Hive
> Issue Type: Improvement
> Components: Configuration
> Reporter: Navis
> Assignee: Navis
> Priority: Minor
> Attachments: HIVE-3946.D8181.1.patch
>
>
> Some MR related configurations like "mapred.reduce.tasks" or
> "hive.exec.reducers.bytes.per.reducer" needed to be configured for each stage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
