Hi team,
Thank you for taking time to verify this RC!
Unfortunately, we didn't get enough votes to go ahead with the release.
Closing this vote as unsuccessful.
Kind regards,
Denys
Thanks for pushing this forward Denys.
A few general comments regarding the procedure.
Every time the artifacts, sources, hashes, or something significant changes
previous casted votes are cancelled. It is usually easier to track this
down by cancelling the RC and starting another.
For traceabil
Hi team,
Thank you for taking time to verify this RC!
Unfortunately, we didn't get enough votes to go ahead with the release.
Closing this vote as unsuccessful.
Kind regards,
Denys
On Fri, Oct 28, 2022, 15:56 Stamatis Zampetakis wrote:
> I think that having a proper NOTICE file in jars is imp
I think that having a proper NOTICE file in jars is important to comply
with the ASF release policy:
* https://www.apache.org/legal/release-policy.html#licensing-documentation
* https://www.apache.org/legal/src-headers.html#notice
* https://www.apache.org/legal/src-headers.html#faq-binaries
The fac
Hi Stamatis,
My bad, sorry. Removed the ".imp" files and updated the release artifacts.*
*** NO CODE CHANGES
I was following the alpha-1 release and the NOTICE wasn't updated there as
well. I don't think that should be a blocker. Noted that + javadoc
artifacts for the new RC.
fc7908f40ec8546
-1 (non-binding)
Ubuntu 20.04.5 LTS, java version "1.8.0_261", Apache Maven 3.6.3
* Verified signatures and checksums OK
* Checked diff between git repo and release sources (diff -qr hive-git
hive-src) KO (among other *.iml files present in release sources but not in
git)
* Checked LICENSE, NOTIC
+1 (non-binding)
* Built from source.
* Verified Checksums.
* Verified Signatures
* Ran some basic unit tests.
* Ran some basic ACID & Iceberg related queries with Tez.
* Skimmed through the Maven Artifacts, Looks Good.
Thanx Denys for driving the release. Good Luck!!!
-Ayush
On Fri, 28 Oct 2022
Extending voting for 24hr. 1 more +1 is needed from the PMC to promote the
release.
If not given, I'll be closing this vote as unsuccessful.
On Thu, Oct 27, 2022 at 11:16 PM Chris Nauroth wrote:
> +1 (non-binding)
>
> * Verified all checksums.
> * Verified all signatures.
> * Built from source.
+1 (non-binding)
* Verified all checksums.
* Verified all signatures.
* Built from source.
* mvn clean install -Piceberg -DskipTests
* Tests passed.
* mvn --fail-never clean verify -Piceberg -Pitests
-Dmaven.test.jvm.args='-Xmx2048m -DJETTY_AVAILABLE_PROCESSORS=4'
I figured out why my tes
You are right Ayush, I got sidetracked by the release notes (* [HIVE-19217]
- Upgrade to Hadoop 3.1.0) and I did not check the versions in the pom
file, apologies for the false alarm but better safe than sorry.
With the right versions in place (Hadoop 3.3.1 and Tez 10.0.2), tests
including select,
Hi Alessandro,
>From this:
> $ sw hadoop 3.1.0
> $ sw tez 0.10.0 (tried also 0.10.1)
I guess you are using the wrong versions, The Hadoop version to be used
should be 3.3.1[1] and the Tez version should be 0.10.2[2]
The error also seems to be coming from Hadoop code
> vertex=vertex_16668880757
Hi everyone,
unfortunately my vote is -1 (although non-binding) due to a classpath error
which prevents queries involving Tez to complete (all the details at the
end of the email, apologies for the lengthy text but I wanted to provide
all the context).
- verified gpg signature: OK
$ wget https:/
Chris,
The KEYS file is at:
https://downloads.apache.org/hive/KEYS
-Ayush
On Thu, 27 Oct 2022 at 21:58, Chris Nauroth wrote:
> Could someone please point me toward the right KEYS file to import so that
> I can verify signatures? Thanks!
>
> I'm seeing numerous test failures due to "Insufficient
Could someone please point me toward the right KEYS file to import so that
I can verify signatures? Thanks!
I'm seeing numerous test failures due to "Insufficient configured threads"
while trying to start the HTTP server. One example is
TestBeelinePasswordOption. Is anyone else seeing this? I noti
Hi,
Thanks for rebuilding this RC, Denys.
Alessandro: IMHO since there was no vote cast yet and we're talking about a
build option change only, I guess it just doesn't worth rebuilding the whole
stuff from scratch to create a new RC.
I give +1 (binding) to this RC, I verified the checksum, bin
Sorry, I have misread the comment.
If the code hasn't changed and the tag for the RC is still pointing to the
same code, I don't think there is a need for a new RC.
On Thu, 27 Oct 2022 at 15:48, Denys Kuzmenko
wrote:
> Hi Alessandro,
>
> There were no code changes, just missing artifacts due to
Hi Alessandro,
There were no code changes, just missing artifacts due to an outdated
release guide (iceberg bits are generated only under iceberg profile).
Not sure that we should create new RC in that case. Naveen, what
do you think?
On Thu, Oct 27, 2022 at 3:30 PM Alessandro Solimando <
alessa
Hi Denys,
in other Apache communities I generally see that votes are cancelled and a
new RC is prepared when there are changes or blocking issues like in this
case, not sure how things are done in Hive though.
Best regards,
Alessandro
On Thu, 27 Oct 2022 at 15:22, Denys Kuzmenko
wrote:
> Hi Ada
Hi Adam,
Thanks for pointing that out! Upstream release guide is outdated. Once I
receive the edit rights, I'll amend the instructions.
Updated the release artifacts and checksums:
Apache Hive 4.0.0-alpha-2 Release Candidate 0 is available
here:https://people.apache.org/~dkuzmenko/release-4.0.0-a
Hi Denys,
Unfortutantely I can't give a plus 1 on this yet, as the Iceberg artifacts are
missing from the binary tar.gz. Perhaps -Piceberg flag was missing during
build, can you please rebuild?
Thanks,
Adam
On 2022/10/25 11:20:23 Denys Kuzmenko wrote:
> Hi team,
>
>
> Apache Hive 4.0.0-alpha
Hi team,
Apache Hive 4.0.0-alpha-2 Release Candidate 0 is available
here:https://people.apache.org/~dkuzmenko/release-4.0.0-alpha-2-rc0/
The checksums are these:
- 7d4c54ecfe2b04cabc283a84defcc1e8a02eed0e13baba2a2c91ae882b6bfaf7
apache-hive-4.0.0-alpha-2-bin.tar.gz
- 8c4639915e9bf649f4a55cd9adb
21 matches
Mail list logo
