I imagine it¹s possible but I¹m not sure it¹s worth the effort. webhcat-site.xml has to be edited during installation anyway since the tar files have to be copied to HDFS to a location that we don¹t know at build time. The values of these properties then depend on the name of the tar files on HDFS.
It would be useful to make sure https://cwiki.apache.org/confluence/display/Hive/WebHCat+InstallWebHCat is up to date w.r.t. how these properties should be set. On 2/18/15, 4:46 PM, "Brock Noland" <br...@cloudera.com> wrote: >We should be able to generate those values in webhcat-default.xml. Eugene? > >On Wed, Feb 18, 2015 at 4:43 PM, Lefty Leverenz <leftylever...@gmail.com> >wrote: >> Four configuration values in webhcat-default.xml need to be updated >>(same >> as HIVE-8807 <https://issues.apache.org/jira/browse/HIVE-8807> updated >>in >> the patch for release 1.0.0 >> >><https://issues.apache.org/jira/secure/attachment/12695112/HIVE8807.patch >>>): >> >> - templeton.pig.path >> - templeton.hive.path >> - templeton.hive.home >> - templeton.hcat.home >> >> How can we make this happen in every release, without reminders? >> >> >> -- Lefty >> >> On Wed, Feb 18, 2015 at 4:04 PM, Brock Noland <br...@cloudera.com> >>wrote: >> >>> Yeah that is really strange. I have seen that before, a long time >>> back, and but not found the root cause. I think it's a bug in either >>> antlr or how we use antlr. >>> >>> I will re-generate the binaries and start another vote. Note the >>> source tag will be the same which is technically what we vote on.. >>> >>> On Wed, Feb 18, 2015 at 3:59 PM, Chao Sun <c...@cloudera.com> wrote: >>> > I tested apache-hive.1.1.0-bin and I also got the same error as >>>Szehon >>> > reported. >>> > >>> > On Wed, Feb 18, 2015 at 3:48 PM, Brock Noland <br...@cloudera.com> >>> wrote: >>> > >>> >> Hi, >>> >> >>> >> >>> >> >>> >> On Wed, Feb 18, 2015 at 2:21 PM, Gopal Vijayaraghavan < >>> gop...@apache.org> >>> >> wrote: >>> >> > Hi, >>> >> > >>> >> > From the release branch, I noticed that the hive-exec.jar now >>> contains a >>> >> > copy of guava-14 without any relocations. >>> >> > >>> >> > The hive spark-client pom.xml adds guava as a lib jar instead of >>> shading >>> >> > it in. >>> >> > >>> >> > >>> >>>https://github.com/apache/hive/blob/branch-1.1/spark-client/pom.xml#L111 >>> >> > >>> >> > >>> >> > That seems to be a great approach for guava compat issues across >>> >> execution >>> >> > engines. >>> >> > >>> >> > >>> >> > Spark itself relocates guava-14 for compatibility with >>> Hive-on-Spark(??). >>> >> > >>> >> > https://issues.apache.org/jira/browse/SPARK-2848 >>> >> > >>> >> > >>> >> > Does any of the same compatibility issues occur when using a >>> >> hive-exec.jar >>> >> > containing guava-14 on MRv2 (which has guava-11 in the classpath)? >>> >> >>> >> Not that I am aware of. I've tested it on top of MRv2 a number of >>> >> times and I think the unit tests also excercise these code paths. >>> >> >>> >> > >>> >> > Cheers, >>> >> > Gopal >>> >> > >>> >> > On 2/17/15, 3:14 PM, "Brock Noland" <br...@cloudera.com> wrote: >>> >> > >>> >> >>Apache Hive 1.1.0 Release Candidate 2 is available here: >>> >> >>http://people.apache.org/~brock/apache-hive-1.1.0-rc2/ >>> >> >> >>> >> >>Maven artifacts are available here: >>> >> >> >>> https://repository.apache.org/content/repositories/orgapachehive-1025/ >>> >> >> >>> >> >>Source tag for RC1 is at: >>> >> >>http://svn.apache.org/repos/asf/hive/tags/release-1.1.0-rc2/ >>> >> >> >>> >> >>My key is located here: >>>https://people.apache.org/keys/group/hive.asc >>> >> >> >>> >> >>Voting will conclude in 72 hours >>> >> > >>> >> > >>> >> >>> > >>> > >>> > >>> > -- >>> > Best, >>> > Chao >>>
