Hi Renjie,
I have modified the google doc setting to allow commenting. Could you try
again when you have time?
Thanks,
Huaxin
On Sun, Feb 18, 2024 at 6:13 PM Renjie Liu wrote:
> Hi, huaxin:
>
> Thanks for raising this discussion. It seems that the doc is read only and
> we can't comment on it.
Hi, Daniel
> 1. I didn't find any docs on how to verify a release (just docs on how to run
> a release). This would be really helpful so that we know what the expected
> setup and steps.
> 2. The license/header checks I did somewhat manually. I also tried using the
> docker/skywalking-eyes, bu
Hi, Jack:
Thanks for raising this.
In most database systems, MV, view and table are considered independent
> objects, at least at API level. It is very rare for a system to support
> operations like "materializing a logical view" or "upgrading a logical view
> to MV", because view and MV are very
>
> A couple things I noticed that might make the verification process go
> smoother:
> 1. I didn't find any docs on how to verify a release (just docs on how to
> run a release). This would be really helpful so that we know what the
> expected setup and steps.
> 2. The license/header checks I did
Hi, huaxin:
Thanks for raising this discussion. It seems that the doc is read only and
we can't comment on it.
I'll take a look at Project Comet and try to see how to integrate it with
iceberg-rust, since they are both written in rust.
On Wed, Feb 14, 2024 at 12:15 PM Holden Karau
wrote:
> T
+1 non-binding
Verified signatures, checksum, and license
Ran unit/integ tests on Python 3.10.4
Ran ad-hoc tests w/ Rest Catalog
Thanks all,
Amogh Jahagirdar
On Sun, Feb 18, 2024 at 4:32 PM Hussein Awala wrote:
> +1 (non-binding)
>
> - Tested the new writing feature with a non-partitioned table
+1 (non-binding)
- Tested the new writing feature with a non-partitioned table
- Created a non-partitioned table using PyArrow Schema
- Tested the new MacOS arm wheel
All looks good!
On Mon, Feb 19, 2024 at 1:20 AM Honah J. wrote:
> +1 (non-binding)
>
> - Verified signatures and checksums
> -
+1 (non-binding)
- Verified signatures and checksums
- Verified license
- Ran unit tests and integration tests
Best regards,
Honah
On Sun, Feb 18, 2024 at 2:54 PM Daniel Weeks
wrote:
> +1 (binding)
>
> Verified sigs/sums/license/tests (python 3.11)
>
> Also ran local tests against Hive and RES
+1 (binding)
Verified sigs/sums/license/tests (python 3.11)
Also ran local tests against Hive and REST catalogs using
appends/overwrites.
-Dan
On Sun, Feb 18, 2024 at 1:37 PM Ryan Blue wrote:
> +1 (binding)
>
> * Checked checksum, signature, recent license changes
> * Built and tested in Pyth
+1 (binding)
* Checked checksum, signature, recent license changes
* Built and tested in Python 3.10
* Ran CLI checks against a REST catalog
Ryan
On Thu, Feb 15, 2024 at 7:55 AM Uwe L. Korn wrote:
> Hello all,
>
> just wanted to give a heads-up that I started publishing the release
> candidate
+1 (binding)
checked sigs/sums/license/build/tests
A couple things I noticed that might make the verification process go
smoother:
1. I didn't find any docs on how to verify a release (just docs on how to
run a release). This would be really helpful so that we know what the
expected setup and st
11 matches
Mail list logo
