+1 (non-binding)
Ran through steps 1-7, completed successfully.
I also updated Nessie to pull from the staging maven repository and ran the
Nessie test suite and it completed successfully with the staged 0.10.0
artifacts.
--
Jacques Nadeau
CTO and Co-Founder, Dremio
On Sat, May 2, 2020 at 8:5
The release vote on the IPMC list has passed! I'll start the process to
publish the release.
-- Forwarded message -
From: Ryan Blue
Date: Wed, May 6, 2020 at 1:06 PM
Subject: [RESULT] [VOTE] Release Apache Iceberg 0.8.0-incubating RC2
To: Owen O'Malley
Cc: Apache
+1 (non-binding)
√ RAT checks passed
√ signature is correct
√ checksum is correct
√ build from source (with java 8)
√ run tests locally
Best,
tison.
Carl Steinbach 于2020年5月3日周日 上午11:09写道：
> +1 (binding)
>
>
> On Fri, May 1, 2020 at 9:38 AM RD wrote:
>
>> +1
>> Validated all the steps mention
+1 (binding)
On Fri, May 1, 2020 at 9:38 AM RD wrote:
> +1
> Validated all the steps mentioned.
>
> -R
>
> On Fri, May 1, 2020 at 9:31 AM Ryan Blue
> wrote:
>
>> +1 (binding)
>>
>> Ran rat, validated checksums and signature, and ran the build.
>>
>> I noticed that the iceberg-spark-runtime Jar
+1
Validated all the steps mentioned.
-R
On Fri, May 1, 2020 at 9:31 AM Ryan Blue wrote:
> +1 (binding)
>
> Ran rat, validated checksums and signature, and ran the build.
>
> I noticed that the iceberg-spark-runtime Jar is about 22MB larger and it
> looks like the problem is mainly that parquet
+1 (binding)
Ran rat, validated checksums and signature, and ran the build.
I noticed that the iceberg-spark-runtime Jar is about 22MB larger and it
looks like the problem is mainly that parquet-avro 1.11.0 is shading all of
fastutil without minimizing the Jar like parquet-column does. I tried
ro
Ran checks on
https://dist.apache.org/repos/dist/dev/incubator/iceberg/apache-iceberg-0.8.0-incubating-rc2/
√ RAT checks passed
√ signature is correct
√ checksum is correct
√ build from source (with java 8)
√ run tests locally
+1 (non-binding)
On Thu, Apr 30, 2020 at 4:18 PM Samarth Jain wrot
+1 (non-binding)
all checks passed
On Thu, Apr 30, 2020 at 4:06 PM John Zhuge wrote:
> +1 (non-binding)
>
>1. Checked signature and checksum
>2. Checked license
>3. Built and ran unit tests.
>
>
> On Thu, Apr 30, 2020 at 2:24 PM Owen O'Malley
> wrote:
>
>> +1
>>
>>1. Checked sig
+1 (non-binding)
1. Checked signature and checksum
2. Checked license
3. Built and ran unit tests.
On Thu, Apr 30, 2020 at 2:24 PM Owen O'Malley
wrote:
> +1
>
>1. Checked signature and checksum
>2. Built and ran unit tests.
>3. Checked ORC version :)
>
> On Monday, ORC rel
+1
1. Checked signature and checksum
2. Built and ran unit tests.
3. Checked ORC version :)
On Monday, ORC released 1.6.3, so we should grab those fixes soon.
.. Owen
On Thu, Apr 30, 2020 at 12:34 PM Dongjoon Hyun
wrote:
> +1.
>
> 1. Verified checksum, sig, and license
> 3. Build fro
+1.
1. Verified checksum, sig, and license
3. Build from the source and run UTs.
4. Run some manual ORC write/read tests with Apache Spark 2.4.6-SNAPSHOT
(as of today).
Thank you, all!
Bests,
Dongjoon.
On Thu, Apr 30, 2020 at 10:28 AM parth brahmbhatt <
brahmbhatt.pa...@gmail.com> wrote:
> +1.
+1. checks passed, did not observe the unit test failure.
Thanks
Parth
On Thu, Apr 30, 2020 at 9:13 AM Daniel Weeks wrote:
> +1 all checks passed
>
> On Thu, Apr 30, 2020 at 8:53 AM Anton Okolnychyi
> wrote:
>
>> That test uses many concurrent writes and I’ve seen cases when it led to
>> deadl
+1 all checks passed
On Thu, Apr 30, 2020 at 8:53 AM Anton Okolnychyi
wrote:
> That test uses many concurrent writes and I’ve seen cases when it led to
> deadlocks in our test HMS. I think HMS is capable of recovering on its own
> but that process can be slow in highly concurrent environments. T
That test uses many concurrent writes and I’ve seen cases when it led to
deadlocks in our test HMS. I think HMS is capable of recovering on its own but
that process can be slow in highly concurrent environments. There is a 2 min
timeout in that test so it can potentially fail. I’ve seen a deadlo
The build for RC2 worked fine for me, I didn't get a failure on
"TestHiveTableConcurrency". Perhaps there is some kind of race condition in
the test? I have seen timeout errors like that when I ran tests on an
overloaded machine, could that have been the case?
On Thu, 30 Apr 2020 at 08:32, OpenInx
I checked the rc2, seems the TestHiveTableConcurrency is broken, may need
to fix it.
1. Download the tarball and check the signature & checksum: OK
2. license checking: RAT checks passed.
3. Build and test the project (java8):
org.apache.iceberg.hive.TestHiveTableConcurrency >
testConcurrentConnec
Hi everyone,
I propose the following candidate to be released as the official Apache
Iceberg 0.8.0-incubating release.
The commit id is 8c05a2f5f1c8b111c049d43cf15cd8a51920dda1
* This corresponds to the tag: apache-iceberg-0.8.0-incubating-rc2
*
https://github.com/apache/incubator-iceberg/commits
17 matches
Mail list logo
