You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hive.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2014/04/04 20:36:14 UTC

[jira] [Updated] (HIVE-6842) Hive should call input/output format methods in a more appropriate place

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

Sergey Shelukhin updated HIVE-6842:
-----------------------------------

    Description: 
While investigating why HBase storage handler works on MR but not Tez (HIVE-6739), I've discovered that the crucial part on MR path that sets some jobconf properties is the call to MapWork::deriveExplainAttributes.
It seems like this should be done in some more appropriate place. 

  was:
While investigating while HBase storage handler works on MR but not Tez (HIVE-6739), I've discovered that the crucial part on MR path that sets some jobconf properties is the call to MapWork::deriveExplainAttributes.
It seems like this should be done in some more appropriate place. 


> Hive should call input/output format methods in a more appropriate place
> ------------------------------------------------------------------------
>
>                 Key: HIVE-6842
>                 URL: https://issues.apache.org/jira/browse/HIVE-6842
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Sergey Shelukhin
>
> While investigating why HBase storage handler works on MR but not Tez (HIVE-6739), I've discovered that the crucial part on MR path that sets some jobconf properties is the call to MapWork::deriveExplainAttributes.
> It seems like this should be done in some more appropriate place. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)