[jira] [Updated] (HIVE-6374) Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly

["Benjamin Zhitomirsky (JIRA)" <ji...@apache.org>]

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

Benjamin Zhitomirsky updated HIVE-6374:
---------------------------------------

    Status: Patch Available  (was: In Progress)

> Hive job submitted with non-default name node (fs.default.name) doesn't process locations properly 
> ---------------------------------------------------------------------------------------------------
>
>                 Key: HIVE-6374
>                 URL: https://issues.apache.org/jira/browse/HIVE-6374
>             Project: Hive
>          Issue Type: Bug
>          Components: CLI
>    Affects Versions: 0.12.0, 0.11.0, 0.13.0
>         Environment: Any
>            Reporter: Benjamin Zhitomirsky
>            Assignee: Benjamin Zhitomirsky
>         Attachments: Design of the fix HIVE-6374.docx, hive-6374.1.patch, hive-6374.3.patch, hive-6374.patch
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Create table/index/database and add partition DDL doesn't work properly if all following conditions are true:
> - Metastore service is used
> - fs.default.name is specified and it differs from the default one
> - Location is not specified or specified as a not fully qualified URI
> The root cause of this behavior is that Hive client doesn't pass configuration context to the metastore services which tries to resolve the paths. The fix is it too resolve the path in the Hive client if fs.default.name is specified and it differs from the default one (it is must easier then start passing the context, which would be a major change).
> The CR will submitted shortly after tests are done



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