Thanks Edward, Brock and Ashutosh for checking out the RC and the inputs!
Brock, you are right, I just checked and found that the RC1 package is
one commit behind the rc1 tag. The package is missing the final commit
that updated the release notes. "r1530840 - Updating RELEASE_NOTES.txt
for commits since 0.12.0 RC0"
Sorry about that! Please let me know if anybody thinks we should
create a new RC with just this fix.
Edward, I have created HIVE-5528 to track the .log file name issue. I
checked 0.11 release as well, it has the same issue. As it is not a
regression, and not a serious issue (such as correctness or serious
performance regression), I think we can include the fix for this in
the next release.
Regarding hive-hwi-0.12.0.war location, it looks like the location has
remained "lib/hive-hwi-0.12.0.war" for a while in
hive-default.xml.template (2010). Maybe your fix is yet to be
committed ? Also, I think we should make then entry in
default.xml.template in sync with what is actually the default in
HiveConf.java (System.getenv("HWI_WAR_FILE")) when we fix the issue.
Regarding the 3 day deadline for voting, that is what is in the hive
bylaws. I also see that has been followed in last few releases I
checked. In my opinion, that is very reasonable, since each release
typically has a few RCs. If we have a 7 day deadline, as most people
have tendency to wait for last day(s) before voting, it can take
several weeks for the release process to finish.
Thanks,
Thejas
On Sat, Oct 12, 2013 at 10:59 AM, Brock Noland <br...@cloudera.com> wrote:
> +1 (non-binding)
>
> Downloaded tar, verified sigs and hashes.
> Tested queries such as create, alter, drop, select, join (via mapjoin
> and reduce side), order by.
> Verified tag and "src" directory of tar.
>
> I noticed the RELEASE NOTES are different from the tarball and the
> tag. I don't think we should block the release for this minor issue.
>
> --- hive-0.12.0/src/RELEASE_NOTES.txt 2013-10-09 20:30:39.000000000 -0500
> +++ release-0.12.0-rc1/RELEASE_NOTES.txt 2013-10-12 12:52:14.720002162 -0500
> @@ -320,7 +320,13 @@
> * [HIVE-5429] - HiveVarcharWritable length not reset when value is
> changed
> * [HIVE-5431] - PassthroughOutputFormat SH changes causes
> IllegalArgumentException
> * [HIVE-5433] - Fix varchar unit tests to work with hadoop-2.1.1
> + * [HIVE-5476] - Authorization-provider tests fail in sequential run
> * [HIVE-5477] - maven-publish fails because it can't find
> hive-metastore-0.12.0.pom
> + * [HIVE-5488] - some files are missing apache license headers
> + * [HIVE-5489] - NOTICE copyright dates are out of date, README needs
> update
> + * [HIVE-5493] - duplicate jars with different versions for guava,
> commons-logging
> + * [HIVE-5497] - Hive trunk broken against hadoop 0.20.2
> +
>
>
>
>
> On Sat, Oct 12, 2013 at 11:59 AM, Ashutosh Chauhan <hashut...@apache.org>
> wrote:
>> Downloaded the tar ball and tested on 1-node pseudo distributed 1.1.2
>> hadoop cluster.
>> Tested basic ddl like create / alter / drop
>> Tested various queries like select, join, group by, over , limit, order etc.
>> Everything worked as expected.
>>
>> +1
>>
>>
>> On Sat, Oct 12, 2013 at 9:33 AM, Brock Noland <br...@cloudera.com> wrote:
>>
>>> I have noticed the ".log" thing for some time. In fact I have PTest2
>>> code to handle this:
>>>
>>>
>>> https://github.com/apache/hive/blob/trunk/testutils/ptest2/src/main/resources/batch-exec.vm#L77
>>>
>>> AFAICT it only occurs in local mode. I have actually fixed this in the
>>> next patch for the maven branch.
>>>
>>> Brock
>>>
>>> On Sat, Oct 12, 2013 at 10:32 AM, Edward Capriolo <edlinuxg...@gmail.com>
>>> wrote:
>>> > I ran a list of queries in local mode, join, select, limit , group, rank,
>>> > they all worked as expected.
>>> >
>>> > I am +1
>>> > It would be nice if we can fix the .log thing and one other (if we do
>>> > another rc)
>>> >
>>> > There is one long standing bug that I feel I have fixed before.
>>> >
>>> > <configuration>
>>> > <property>
>>> > <name>hive.hwi.war.file</name>
>>> > <value>lib/hive-hwi-0.12.0.war</value>
>>> > <description>This sets the path to the HWI war file, relative to
>>> > ${HIVE_HOME}. </description>
>>> > </property>
>>> > </configuration>
>>> >
>>> >
>>> > This should be
>>> >
>>> > /lib/hive-hwi-0.12.0.war
>>> >
>>> > Other then that hive_web interface does work out of the box.
>>> >
>>> >
>>> > On Fri, Oct 11, 2013 at 11:32 PM, Thejas Nair <the...@hortonworks.com
>>> >wrote:
>>> >
>>> >> Hoping to see more activity on this thread!
>>> >>
>>> >> I have run the unit tests and they passed with the exception of one
>>> >> test in TestThriftHttpCLIService, which fails only when run in
>>> >> sequence with TestThriftBinaryCLIService. It passes when run in
>>> >> parallel/standalone. That is not a regression, see HIVE-5474 for
>>> >> details. None of the runs on builds.apache.org have completed because
>>> >> of some environment issues.
>>> >>
>>> >>
>>> >> I would like to clarify that you don't have to be a committer or PMC
>>> >> member to give feedback on the release candidate. So please try it out
>>> >> and give feedback on the mailing list.
>>> >>
>>> >> Somethings you can try out and use to give feedback -
>>> >> - run some queries against the release candidate (local mode or
>>> >> against a cluster)
>>> >> - run some or all unit tests
>>> >> - verify the md5 checksums
>>> >>
>>> >> % md5sum -c hive-X.Y.Z.tar.gz.md5
>>> >> hive-X.Y.Z.tar.gz: OK
>>> >>
>>> >> % md5sum -c hive-X.Y.Z-bin.tar.gz.md5
>>> >> hive-X.Y.Z-bin.tar.gz: OK
>>> >>
>>> >>
>>> >> - verify the PGP signature
>>> >> wget http://www.apache.org/dist/hive/KEYS
>>> >> gpg --import KEYS (if necessarily)
>>> >> gpg --verify hive-X.Y.Z.tar.gz.asc hive-X.Y.Z.tar.gz
>>> >> gpg --verify hive-X.Y.Z-bin.tar.gz.asc hive-X.Y.Z-bin.tar.gz
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> On Wed, Oct 9, 2013 at 7:50 PM, Thejas Nair <the...@hortonworks.com>
>>> >> wrote:
>>> >> > (Fixing subject of the email!)
>>> >> >
>>> >> > On Wed, Oct 9, 2013 at 7:31 PM, Thejas Nair <the...@hortonworks.com>
>>> >> wrote:
>>> >> >> Apache Hive 0.12.0 Release Candidate 1 is available here:
>>> >> >>
>>> >> >> http://people.apache.org/~thejas/hive-0.12.0-rc1/
>>> >> >>
>>> >> >> Maven artifacts are available here:
>>> >> >>
>>> >> >>
>>> https://repository.apache.org/content/repositories/orgapachehive-157/
>>> >> >>
>>> >> >> Source tag for RC1 is at:
>>> >> >> http://svn.apache.org/viewvc/hive/tags/release-0.12.0-rc1/
>>> >> >>
>>> >> >> Voting will conclude in 72 hours.
>>> >> >>
>>> >> >> Hive PMC Members: Please test and vote.
>>> >> >>
>>> >> >> This RC includes the following jira fixes to address some of the
>>> >> >> concerns raised about RC0 -
>>> >> >> HIVE-5497 : Hive trunk broken against hadoop 0.20.2
>>> >> >> HIVE-5493 : duplicate jars with different versions for guava,
>>> >> commons-logging
>>> >> >> HIVE-5489 : NOTICE copyright dates are out of date, README needs
>>> update
>>> >> >> HIVE-5488 : some files are missing apache license headers
>>> >> >>
>>> >> >> Thanks to all everybody who made this new release possible. Thanks to
>>> >> >> everybody who reviewed RC0.
>>> >> >>
>>> >> >> Thanks
>>> >> >> Thejas
>>> >>
>>> >> --
>>> >> CONFIDENTIALITY NOTICE
>>> >> NOTICE: This message is intended for the use of the individual or
>>> entity to
>>> >> which it is addressed and may contain information that is confidential,
>>> >> privileged and exempt from disclosure under applicable law. If the
>>> reader
>>> >> of this message is not the intended recipient, you are hereby notified
>>> that
>>> >> any printing, copying, dissemination, distribution, disclosure or
>>> >> forwarding of this communication is strictly prohibited. If you have
>>> >> received this communication in error, please contact the sender
>>> immediately
>>> >> and delete it from your system. Thank You.
>>> >>
>>>
>>>
>>>
>>> --
>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
>>>
>
>
>
> --
> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.
