[
https://issues.apache.org/jira/browse/HIVE-17621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184594#comment-16184594
]
Mithun Radhakrishnan commented on HIVE-17621:
---------------------------------------------
The failures are known to be fickle, and are unrelated to the fix at hand. The
[build logs in
HIVE-12734|https://issues.apache.org/jira/browse/HIVE-12734?focusedCommentId=16183670&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16183670]
indicate that master is alright as well.
I'll rebase this, and run a some sanity checks before checking this in.
> Hive-site settings are ignored during HCatInputFormat split-calculation
> -----------------------------------------------------------------------
>
> Key: HIVE-17621
> URL: https://issues.apache.org/jira/browse/HIVE-17621
> Project: Hive
> Issue Type: Bug
> Components: HCatalog
> Affects Versions: 2.2.0, 3.0.0
> Reporter: Mithun Radhakrishnan
> Assignee: Chris Drome
> Attachments: HIVE-17621.1-branch-2.2.patch,
> HIVE-17621.1-branch-2.patch, HIVE-17621.1.patch
>
>
> Another one that [~selinazh] and [~cdrome] worked on.
> The production {{hive-site.xml}} could well contain settings that differ from
> the defaults in {{HiveConf.java}}. In our case, we introduced a custom ORC
> split-strategy, which we introduced as the site-wide default.
> We noticed that during {{HCatInputFormat::getSplits()}}, if the user-script
> did not contain the setting, the site-wide default was ignored in favour of
> the {{HiveConf}} default. HCat would not convey hive-site settings to the
> input-format (or anywhere downstream).
> The forthcoming patch fixes this problem.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
