-1 due to the ORC correctness bug. I’ll build a new RC.
Thanks everyone for checking the candidate!
- Anton
> On 2 Nov 2020, at 19:01, Ryan Blue wrote:
>
> I think we are going to build another RC to get the ORC correctness problem
> that Shardul just fixed in.
>
> On Mon, Nov 2, 2020 at 6:4
I think we are going to build another RC to get the ORC correctness problem
that Shardul just fixed in.
On Mon, Nov 2, 2020 at 6:40 PM Jingsong Li wrote:
> +1
>
> 1. Download the source tarball, signature (.asc), and checksum (.sha512):
> OK
> 2. Import gpg keys: download KEYS and run gpg --imp
+1
1. Download the source tarball, signature (.asc), and checksum (.sha512):
OK
2. Import gpg keys: download KEYS and run gpg --import
/path/to/downloaded/KEYS (optional if this hasn’t changed) : OK
3. Verify the signature by running: gpg --verify
apache-iceberg-xx-incubating.tar.gz.asc: OK
4.
Hi Ryan
Got your plan ! If we plan to release 0.11.0 in November tentatively, then
for flink I think we could finish the rewrite actions and flink streaming
reader firstly.
The flink cdc integration work and FLIP-27 would need more work, it's good
to not block the release 0.11.0. But we could sti
Anton, thanks for the interest. It's across modules, and looks to be
consistent. Looks like others have no problem with UT runs, probably need
to have another mail thread or Github issue for this.
On Tue, Nov 3, 2020 at 1:31 AM Anton Okolnychyi
wrote:
> Jungtaek, do you hit this issue only in a
Thanks for starting the 0.11.0 milestone! In the last sync, we talked about
having a release in November to make the new catalogs and possibly S3FileIO
available, so those should tentatively go on the 0.11.0 list as well. I say
tentatively because I'm in favor of releasing when features are ready a
Jungtaek, do you hit this issue only in a specific suite/module? Is it
consistent?
I remember we had similar issues for our Spark tests. If I am not mistaken, the
underlying problem was related to the number of connections we were making to
HMS and the pool size that was configured in our test
+1 (non-binding)
Ran through steps 1-7, completed successfully. Also tested locally against
nessie and all looked good.
Best,
Ryan
On Mon, Nov 2, 2020 at 2:28 PM Mass Dosage wrote:
> +1 (non-binding)
>
> I ran the RC against a set of integration tests I have for a subset of the
> Hive2 read fu
+1 (non-binding)
I ran the RC against a set of integration tests I have for a subset of the
Hive2 read functionality on a distributed cluster and it worked fine.
On Mon, 2 Nov 2020 at 04:05, Simon Su wrote:
> + 1 (non-binding)
> 1. Build code pass all UTs.
> 2. Test Flink iceberg sink failover,
Probably not a good thread to ask, but encounter the issue again during
verification of RC so asking here:
I'm consistently encountering multiple test failures due to HMS. It
shouldn't matter as others verified the UTs, but if someone is aware of the
issue and the resolution (or at least where to
10 matches
Mail list logo
