Thanks for the feedback Stamatis!
As discussed offline:
I will close this vote as unsuccessful
I will create a new release candidate with the
derby.log/metastore_db/${test.tmp.dir} removed, but keep the other things
unchanged
I have created jiras to fix the other issues in the next release:
HIVE
Ubuntu 20.04.4 LTS, jdk1.8.0_261, Apache Maven 3.6.3
* Checked signatures and checksums OK
* Checked diff between repo and release sources (diff -qr hive
apache-hive-4.0.0-alpha-1-src) KO
* Built from git tag (mvn clean install -DskipTests -Pitests) OK
* Built from release sources (mvn clean i
Hi Stamatis,
Here is the data you have suggested:
Commit hash: 357d4906f5c806d585fd84db57cf296e12e6049b
Checksums:
ff60286044d2f3faa8ad1475132cdcecf4ce9ed8faf1ed4e56a6753ebc3ab585
apache-hive-4.0.0-alpha-1-bin.tar.gz
07f30371df5f624352fa1d0fa50fd981a4dec6d4311bb340bace5dd7247d3015
apache-hive-
Did some checking.
The issue you have faced is only present if the DB version is 4.0.0, and we are
running 4.0.0-alpha-1 code.
This will not happen if the user is using released Hive versions until they try
to upgrade from 4.0.0-alpha-1 to 4.0.0-alpha-2, or 4.0.0.
So I think we should not stop
After I upgrade, the issue is gone.
+1 (non-binding)
* Rat check: ok
- mvn clean apache-rat:check
* Build from source (1.8.0_312): ok
- mvn install -Pdist -DskipTests -Dmaven.javadoc.skip=true
* Test simple queries on pseudo cluster with Hadoop 3.1.0(tez & mr), all good.
- create db
I think you forgot to upgrade the metastore schema.
We might want to provide a better error message.
> On 2022. Mar 23., at 8:14, dengzhhu653 wrote:
>
>
>
>
> * Rat check: ok
> - mvn clean apache-rat:check
> * Build from source (1.8.0_312): ok
> - mvn install -Pdist -DskipTests -Dmaven.ja
* Rat check: ok
- mvn clean apache-rat:check
* Build from source (1.8.0_312): ok
- mvn install -Pdist -DskipTests -Dmaven.javadoc.skip=true
* Test simple queries on pseudo cluster with Hadoop 3.1.0(tez & mr), but failed
to bring up the embedded metastore.
java.lang.NumberFormatExceptio
Hi Peter,
Many thanks for rolling out the RC and for resolving many of the blocker
issues that were remaining.
In general, it is a good practice to include the commit hash (which tags
the release) and the checksum hashes of the release artifacts [1] in the
vote email to minimize the chances of ma
I have been able to build and run a quick test. I have NOT verified the
signature. I was trying to run the HMS Checkin tests and got this. I
suspect these are not specific to the alpha-1 branch. But it is not a test
failure (although it appears like it should be)
*"mvn test
-Dtest.groups=org.apache
+1 (non-binding)
Tested the checksums, signatures and built it successfully
On Tue, Mar 22, 2022 at 2:26 PM Peter Vary
wrote:
> Hi Team,
>
> Apache Hive 4.0.0-alpha-1 Release Candidate 1 is available here:
>
> https://people.apache.org/~pvary/apache-hive-4.0.0-alpha-1-rc1/
>
> Maven artifacts ar
Hi Team,
Apache Hive 4.0.0-alpha-1 Release Candidate 1 is available here:
https://people.apache.org/~pvary/apache-hive-4.0.0-alpha-1-rc1/
Maven artifacts are available here:
https://repository.apache.org/content/repositories/orgapachehive-/
The tag 4.0.0-alpha-1-rc1 has been applied to the
11 matches
Mail list logo
