Re: [VOTE] Apache Hive 1.2.0 release candidate 2

2015-05-11 Thread Sushanth Sowmyan
I've filed https://issues.apache.org/jira/browse/HIVE-10674 to track removal of the checked-in jars on master, and their eventual restoration via a download & test-compile target. For branch-1.2, I have git rm-ed the above 2 jars, and 2 more that I found. These will cause some limited test failure

Re: [VOTE] Apache Hive 1.2.0 release candidate 2

2015-05-11 Thread Alan Gates
I'm fine with doing this for the release, but I think we should apply the fix to branch-1.2 after the release so that any subsequent patches applied to this branch don't have to deal with the failing tests. Alan. Sushanth Sowmyan May 11, 2015 at 12:01 Thanks for th

Re: [VOTE] Apache Hive 1.2.0 release candidate 2

2015-05-11 Thread Sushanth Sowmyan
Thanks for the catch, Alan. Looks like the 2 jars got added via HIVE-9302, and are being used as resources for beeline tests. We could attempt to change the postgres jar to a download, but I don't know where the DummyDriver is coming from. They really should not have been checked in, imo. (we sho

Re: [VOTE] Apache Hive 1.2.0 release candidate 2

2015-05-11 Thread Alan Gates
-1 A couple of jar files found there way into the src release: gates> find . -name \*.jar ./beeline/src/test/resources/DummyDriver-1.0-SNAPSHOT.jar ./beeline/src/test/resources/postgresql-9.3.jdbc3.jar We can't have any binaries in the source release. In the README: * At what point is the @VERS

Re: [VOTE] Apache Hive 1.2.0 release candidate 2

2015-05-11 Thread Sushanth Sowmyan
(Slight correction, the source tag link is for RC2, which is the correct link) On Mon, May 11, 2015 at 10:14 AM, Sushanth Sowmyan wrote: > Hi Folks, > > We've cleared all the blockers listed for 1.2.0 release, either > committing them, or deferring out to an eventual 1.2.1 stabilization > releas

[VOTE] Apache Hive 1.2.0 release candidate 2

2015-05-11 Thread Sushanth Sowmyan
Hi Folks, We've cleared all the blockers listed for 1.2.0 release, either committing them, or deferring out to an eventual 1.2.1 stabilization release. (Any deferrals were a result of discussion between myself and the committer responsible for the issue.) More details are available here : https://