Re: [VOTE] Release Apache PyIceberg 0.6.1rc2

Thanks everyone for voting! Thanks Dan for reporting the issue and Fokko for the context! Let's do another RC to include the https://github.com/apache/iceberg-python/pull/615. Some additional note: In our case, this issue only affects the release dist because it does not contain the poetry.lock fi

Re: [VOTE] Release Apache PyIceberg 0.6.1rc2

Thanks everyone for voting. And Dan, thanks for reporting the issue. I went down the rabbit hole 🐇 It is being tracked here , and a fix is inbound here . This issue should fix itself because the version c

Re: [VOTE] Release Apache PyIceberg 0.6.1rc2

+1 (non binding) Downloaded specific commit from the repo, and ran both the Python tests and integration tests. Steps: ``` git clone --depth=1 --branch pyiceberg-0.6.1rc2 g...@github.com: apache/iceberg-python.git python -m venv ./venv source ./venv/bin/activate make install make test make test-i

Re: [VOTE] Release Apache PyIceberg 0.6.1rc2

I tried running the verification process but ran into issues resolving some of the dependencies: make install Updating dependencies Resolving dependencies... (3.1s) Package docutils (0.21.post1) not found. make: *** [install-dependencies] Error 1 I found this related issue

Re: [VOTE] Release Apache PyIceberg 0.6.1rc2

+1 (non binding) I checked: - Hash and signature are good - LICENSE and NOTICE look good - No binary file found in the source distribution - Ran a few tests Regards JB On Tue, Apr 16, 2024 at 4:53 AM Honah J. wrote: > > Hi Everyone, > > I propose that we release the following RC as the official

Re: [VOTE] Release Apache PyIceberg 0.6.1rc2

Hey everyone, First of all, thanks Honah for running the release! +1 (binding) from my end - I checked the signature, hashes, and licenses and all look good . - Ran some local tests. Kind regards, Fokko Op di 16 apr 2024 om 05:55

Re: Flink table maintenance

Hi Gen, Thanks for your interest and thoughts! See my answers and questions below: Gen Luo ezt írta (időpont: 2024. ápr. 17., Sze, 20:32): > Hi, > > Sorry for joining the discussion so late. I'm from the flink community and > did some work about the SinkV2. I'd like to share some thoughts from

Re: Flink table maintenance

Hi, Sorry for joining the discussion so late. I'm from the flink community and did some work about the SinkV2. I'd like to share some thoughts from the view of flink. While I'm quite new to Iceberg, please feel free to correct me if I'm making any mistakes. 1. checkpointing I think the maintenanc

Query regarding UPSERT Mode in Flink

Hi all, In Flink SQL, in UPSERT mode, I have observed that if I INSERT a new record with a new equality field Id, then a equality delete file is also created with the corresponding entry, for example I executed following commands in Flink SQL with Apache Iceberg- CREATE TABLE `hadoop_catalog`

Re: Materialized view integration with REST spec

As an update, there is more common understanding now of the options in the doc. Please feel free to take another look. The most relevant comment at this point is this comment . Based on thi

Re: spec question on equality deletes

+1 on defining it clearly in the spec. Note the “spec doc” is the spec itself, which requires more accurate description than doc. We may also need spec test to check whether compute engine conforms to spec, not the other way around. Yufei Gu 于2024年4月17日 周三01:08写道： > For me, (b) is the right behav

Re: Materialized view integration with REST spec

Kindly remind to review and discuss the proposal in doc. On Thu, Apr 4, 2024 at 9:22 PM Jean-Baptiste Onofré wrote: > Just to clarify: I think we have a consensus on the two possible > options. So the vote could be helpful to have a consensus about which > option. > > Anyway, we still have discu

Re: Streamlining the monitoring of active projects/proposals

Hi, Ajantha: Sounds good to me. On Tue, Apr 16, 2024 at 7:43 PM Jean-Baptiste Onofré wrote: > Yes, it sounds good. Let's see what the others are thinking. > > Thanks, > Regards > JB > > On Tue, Apr 16, 2024 at 10:33 AM Ajantha Bhat > wrote: > > > > Yeah, > > I would call them "subtasks" with o