[
https://issues.apache.org/jira/browse/HIVE-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sushanth Sowmyan updated HIVE-4278:
-----------------------------------
Attachment: HIVE-4278.approach2.patch
Hi folks, I tried another approach that might hopefully be acceptable, and have
uploaded a patch for that.
The premise:
a) We want to unblock HCat's ability to build from inside hive, picking the
latest jars hive builds.
b) We want to do this without changing how the hive workflow looks like,
including not changing publishing to the current ivy cache dir.
c) We don't want to perform invasive surgery to HCat switching it back to ivy
either, till we can form a consensus as to which build tool we should
standardize around.
Assumption:
a) Builtins can be removed ( HIVE-4304 and hive-dev mailing list discussion )
or, rather, at least, in the meanwhile, be disabled as a transitive dependency
from other targets.
b) It is okay for hcat, during its build, to look at the jars hive has just
built, and publish that to the local maven cache.
Future work:
a) Trying to unify version numbers between hcat and hive - I'm still unhappy
about the number of files in which the string "0.12.0-SNAPSHOT" occurs.
Is this compromise acceptable to all? Thoughts?
> HCat needs to get current Hive jars instead of pulling them from maven repo
> ---------------------------------------------------------------------------
>
> Key: HIVE-4278
> URL: https://issues.apache.org/jira/browse/HIVE-4278
> Project: Hive
> Issue Type: Sub-task
> Components: Build Infrastructure, HCatalog
> Affects Versions: 0.11.0
> Reporter: Alan Gates
> Assignee: Travis Crawford
> Priority: Blocker
> Fix For: 0.11.0
>
> Attachments: HIVE-4278.approach2.patch, HIVE-4278.D9981.1.patch
>
>
> The HCatalog build is currently pulling Hive jars from the maven repo instead
> of using the ones built as part of the current build. Now that it is part of
> Hive it should use the jars being built instead of pulling them from maven.
--
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
