Re: [VOTE] Update the table statistics (puffin stats) spec

I agree that this should have been a long in the spec, so +1 to fixing the spec. I checked and Trino also implements this as a long. On Mon, Jul 28, 2025 at 12:39 PM Ajantha Bhat wrote: > Hi everyone, > One of the users has raised a PR to update the table statistics (puffin > stats) spec. > http

Re: [DISCUSS] Iceberg Summit NA 2026 and Iceberg Summit EU 2026 ?

+1 to having an EU summit On Mon, Jul 28, 2025 at 9:57 AM Claude Warren, Jr wrote: > +1 > > I would be inclined to attend an EU summit but not a NA one. > > I was chair of the ASF Community over Code EU 2024 and am willing to help > organize, though I do not have time to act as chair. > > Claud

Re: Iceberg 1.10.0 release update - July 1, 2025

I believe we also wanted to get in at least the read path for UnknownType. Fokko has a WIP PR for that. On Fri, Jul 25, 2025 at 6:13 PM Steven Wu wrote: > 3. Spark: fix data frame join based on different versions of the same > table that may lead to

Re: [DISCUSS] v4 - Improved column statistics

>1. The current proposal only leaves 1+200 ids for other columns >than stats. If in the future, we find some other feature which would >require a manifest file column for every data column in the table, then we >would need to change the spec. > > For this I think we could start

Re: [ANNOUNCE] Welcome Prashant Singh as a new Apache Iceberg Committer

Congrats Prashant, very well deserved! On Wed, Jul 23, 2025 at 5:43 AM Renjie Liu wrote: > Congrats, Prashant! > > On Wed, Jul 23, 2025 at 11:21 AM Prashant Singh > wrote: > >> Thank you everyone, >> >> I'm truly grateful to be part of the Apache Iceberg community and excited >> to continue con

Re: [ANNOUNCE] Apache Iceberg release 1.9.2

Yes, the latest release should show up there, which I've just published. Thanks everyone On Fri, Jul 18, 2025 at 3:26 PM Robin Moffatt wrote: > Thanks for driving the release! > > A quick question - should it show up on > https://github.com/apache/iceberg/releases ? Currently it's showing 1.9.1

Re: [DISCUSS] v4 - Improved column statistics

oEfo/edit?usp=sharing> . Thanks everyone, Eduard On Tue, Jul 8, 2025 at 6:51 PM Eduard Tudenhöfner wrote: > Hey everyone, > > I've just added an event to the dev calendar for July 15 at 9am (PT) to > discuss the column stats proposal. > > > Eduard > > On

Re: [DISCUSS] v4 - Improved column statistics

Hey everyone, I've just added an event to the dev calendar for July 15 at 9am (PT) to discuss the column stats proposal. Eduard On Tue, Jul 8, 2025 at 4:09 AM Jacky Lee wrote: > +1 for the wonderful feature. Please count me in if you need any help. > > Gábor Kaszab 于2025年

Re: [DISCUSS] Remove usage of allowEmptyValue

I'm +1 on removing it. On Tue, Jun 10, 2025 at 7:03 PM Elphas Toringepi wrote: > Hi Team, > > I’d like to start a discussion about removing the use of allowEmptyValue > in the REST Catalog API, in light of OAI/OpenAPI-Specification#1632. > > The use of allowEmptyValue is not recommended, and it

Re: Apply spotless for scala code

I've reviewed the changes and they LGTM. Since we can fully control the max line length for the Scala code, I would probably update it from 100 to 120 or 140 to get more stuff on a single line. What do people think about adjusting the max line length? On Tue, Jun 24, 2025 at 1:51 PM Liu Xianyan

Re: [DISCUSS] Restructuring Docs side navigation

I do agree that we need to restructure the site to make things less cluttered and easier to find. Thanks Manu/Peter for working on this. It would be great to have a few more reviewers that can help out here and add their opinions about the restructure. Thanks Eduard On Thu, Jun 5, 2025 at 3

[DISCUSS] v4 - Improved column statistics

es (e.g., complex types like Geo/Variant). Thanks Eduard

Re: [VOTE][Go] Release Apache Iceberg Go v0.3.0 RC0

+1 (binding) Thanks everyone! On Thu, May 22, 2025 at 12:19 AM Leon Lin wrote: > +1 (non-binding) > > Thank you Matt for running the release! > > On Wed, May 21, 2025 at 10:32 AM Kevin Liu wrote: > >> +1 (non-binding) >> >> [x] Download links are valid. >> [x] Checksums and signatures. >> [x]

Re: [VOTE] Release Apache Iceberg Rust 0.5.0 RC2

+1 (binding) I think it would be beneficial if the Rust Release docs would have something similar to https://iceberg.apache.org/how-to-release/#how-to-verify-a-release on how to verify an RC. Thanks everyone! On Mon, May 26, 2025 at 9:54 AM Renjie Liu wrote: > +1 binding > > [x] Download links

Re: [RESULT][VOTE] Merge details about GZip metadata files to the spec.

t;>>> +1 (binding) >>>>>> >>>>>> Thanks >>>>>> Szehon >>>>>> >>>>>> On Mon, May 12, 2025 at 9:19 AM Russell Spitzer < >>>>>> russell.spit...@gmail.com> wrot

Re: [VOTE] [REST SPEC] Add row lineage fields.

+1 (binding) On Fri, May 23, 2025 at 1:19 AM Steven Wu wrote: > +1 (binding) > > On Thu, May 22, 2025 at 3:39 PM Prashant Singh > wrote: > >> Hi All, >> I propose an update to the Rest Spec to include the Row lineage fields. >> As these need to be passed from server to client for reads, as it i

Re: [VOTE] Adopt the v3 spec changes

+1 (binding) On Tue, May 20, 2025 at 8:14 AM Gidon Gershinsky wrote: > +1 (non-binding). > Glad to see this big step forward. > > Cheers, Gidon > > > On Tue, May 20, 2025 at 9:00 AM Ajantha Bhat > wrote: > >> +1 (non-binding) >> >> Excited to see Iceberg V3 coming together! >> >> - Ajantha >> >

Re: [VOTE] Clarify writer requirements in the spec to prevent orphan DVs

+1 (binding) On Wed, May 14, 2025 at 5:52 PM Anton Okolnychyi wrote: > Hi all, > > I propose the following update to the spec to clarify that writers must > remove any deletion vector that applies to a data file when that data file > is removed from the metadata, as previously brought up by Stev

Re: [VOTE] Merge details about GZip metadata files to the spec.

+1 (binding) On Mon, May 12, 2025 at 3:45 AM Gang Wu wrote: > +1 (non-binding) > > On Mon, May 12, 2025 at 3:27 AM Kevin Liu wrote: > >> +1 (non-binding) >> >> Thanks for starting a vote. >> >> There's extra context in the PR description. As a summary, >> `gz.metadata.json` is the current namin

Re: [VOTE] Add encryption key updates to REST spec

+1 (binding) On Thu, May 8, 2025 at 5:23 PM Ryan Blue wrote: > Hi everyone, > > I’d like to raise a vote for committing PR 12987 > that adds table updates > for encryption keys, AddEncryptionKey and RemoveEncryptionKey. These are > needed to maintai

Re: [VOTE] Minor clarification for Geo Spec

+1 (binding) On Wed, May 7, 2025 at 4:14 AM Gang Wu wrote: > The clarification is simple and clear from the writer's perspective. > > CMIW, the implication is that reader should drop bbox with any NaN value > regardless of the coordinate axis (in case of a writer bug). > > On Wed, May 7, 2025 at

Re: [VOTE] Release Apache PyIceberg 0.9.1rc1

+1 (binding) checked license and unit/integration tests. I've had a few failing tests related to ray. tests/integration/test_reads.py::test_ray_nan_rewritten[session_catalog_hive] FAILED tests/integration/test_reads.py::test_ray_nan_rewritten[session_catalog] FAILED tests/integration/test_read

Re: [VOTE] Add encryption keys to table metadata

+1 (binding) On Tue, Apr 29, 2025 at 9:29 PM Ryan Blue wrote: > Hi everyone, > > I’d like to propose merging PR 12162 > into the table spec > for v3. The changes are a minimal set of additions needed to support table > encryption schemes, incl

Re: [VOTE] Release Apache Iceberg 1.9.0 RC2

+1 (binding) * checked signatures / checksum * ran tests using JDK 17 * ran Spark quickstart examples and a few manual tests Thanks for running the release Ajantha. Eduard On Fri, Apr 25, 2025 at 3:22 PM Fokko Driesprong wrote: > +1 (binding) > > - Checked the signatures, che

Re: [VOTE] Small spec change for default values

+1 On Tue, Apr 22, 2025 at 7:31 AM Jean-Baptiste Onofré wrote: > +1 (non binding) > > Regards > JB > > On Mon, Apr 21, 2025 at 11:20 PM Ryan Blue wrote: > > > > Hi everyone, > > > > I’d like to vote on the spec changes in PR 12841. This is a small change > that makes handling default values for

Re: [DISCUSS] Table Identifiers in Iceberg View Spec

Thanks Walaa for tackling this problem. I've added a few comments to get a better understanding of how this will look like in the actual implementation. Eduard On Tue, Apr 15, 2025 at 7:09 PM Walaa Eldin Moustafa wrote: > Hi Everyone, > > Starting this thread to resume our discus

Re: [DISCUSS] Inconsistent NoSuchNamespaceException handling in REST Catalog API specification

whether others think it would be worth updating this but so far I think we should just stick to the existing behavior. Thanks Eduard On Fri, Apr 4, 2025 at 11:24 AM Паша Варченко wrote: > Hello! > Apache Iceberg REST Catalog API specification has many handlers that > contain namespace na

Re: [DISCUSS] Introducing Iceberg Features ?

ports. Eduard On Wed, Apr 16, 2025 at 8:23 AM Jean-Baptiste Onofré wrote: > Hi Xuanwo > > Thanks for the feedback. Fair enough. > > Regards > JB > > Le mer. 16 avr. 2025 à 05:44, Xuanwo a écrit : > >> Hi, JB >> >> Thank you for starting this discussi

Re: [DISCUSS] Fix CVE-2025-30065 on 1.8.x / 1.7.x / 1.6.x?

So it sounds like we may want to do 1.8.2 with the updated Parquet version as that should be very low risk. Does anyone want to volunteer and be the release manager for 1.8.2? On Mon, Apr 14, 2025 at 5:29 PM Ryan Blue wrote: > I agree with Fokko. It's a good idea to get a release out soon that h

Re: [VOTE] Release Apache Iceberg 1.9.0 RC0

gt; * > https://repository.apache.org/content/repositories/orgapacheiceberg-1188/ > > > > Please download, verify, and test. > > > > Please vote in the next 72 hours. > > > > [ ] +1 Release this as Apache Iceberg 1.9.0 > > [ ] +0 > > [ ] -1 Do not

Re: [VOTE] Improve OpenAPI documentation around how NamespaceNotEmptyException is treated

>>> On Fri, Mar 14, 2025 at 10:17 AM Jean-Baptiste Onofré >>> wrote: >>> >>>> +1 (non binding) >>>> >>>> Regards >>>> JB >>>> >>>> On Fri, Mar 14, 2025 at 3:10 PM Eduard Tudenhöfner >>>> wro

Re: [VOTE] Row lineage required for v3

+1 On Tue, Apr 1, 2025 at 8:07 AM Jean-Baptiste Onofré wrote: > +1 (non binding) > > Regards > JB > > On Mon, Mar 31, 2025 at 8:42 PM Daniel Weeks wrote: > > > > Hey Everyone, > > > > I'd like to raise the proposal to make row-lineage required by default > to a vote. > > > > There was general s

Re: [DISCUSS] Change iceberg-cpp CI settings to only require approval for new contributors

+1 On Mon, Mar 31, 2025 at 11:39 AM Renjie Liu wrote: > Thanks Gang for this proposal, +1 for this change. > > On Mon, Mar 31, 2025 at 4:50 PM Xuanwo wrote: > >> Here is my +1 non-binding. >> >> I'm watching on this repo actively and will make sure the CI won't be >> abused. >> >> On Mon, Mar 3

Re: [VOTE][Go] Release Apache Iceberg Go v0.2.0 RC1

+1 (binding) * ran the verification script * ran a few local tests against a REST catalog Thanks everyone On Tue, Mar 25, 2025 at 7:48 PM Fokko Driesprong wrote: > +1 (binding) > > Thanks for running this release Matt, and for adding the additional tests! > > Checked the V1/V2 metadata/manifes

Re: [DISCUSS] Row lineage required for v3

I'm convinced that always having lineage metadata is the right call, so I'm +1 here. On Thu, Mar 20, 2025 at 11:15 PM Ryan Blue wrote: > Now, if we make it required for V3 tables, what if users don’t need the > row lineage feature. There is a bit overhead (although low) for row > lineage. E.g.,

Re: [VOTE] Improve OpenAPI documentation around how NamespaceNotEmptyException is treated

gt; > On Tue, Mar 18, 2025 at 5:11 PM Daniel Weeks wrote: > >> +1 as well for 409 >> >> On Tue, Mar 18, 2025 at 1:43 PM Ryan Blue wrote: >> >>> +1 for the updated 409 code. >>> >>> On Tue, Mar 18, 2025 at 1:41 PM Yufei Gu wrote: >>&g

Re: [VOTE] Minor simplifications for Geo Spec

+1 On Wed, Mar 19, 2025 at 2:30 AM Gang Wu wrote: > Makes sense. > > +1 (non-binding) > > On Wed, Mar 19, 2025 at 8:07 AM Jia Yu wrote: > >> +1 (non-binding) >> >> Thank you! >> >> On 2025/03/19 00:01:00 Szehon Ho wrote: >> > Hi everyone, >> > >> > While working on the reference implementation

Re: [VOTE] Release Apache Iceberg 1.7.2 RC3

+1 (binding) verified sigs/checksums/tests On Wed, Mar 19, 2025 at 4:58 AM Russell Spitzer wrote: > +1 (binding) > verified sigs, checksums, rat. Ran Build/test > > On Tue, Mar 18, 2025 at 10:45 PM Amogh Jahagirdar <2am...@gmail.com> > wrote: > >> +1 (binding) >> verified signatures/checksums/R

Re: [DISCUSS] Inconsistency between java implementation and spec about partition-spec and schema in v1 table

that the problem is with how Glue produces V1 metadata. Eduard On Tue, Mar 18, 2025 at 9:53 AM Fokko Driesprong wrote: > Hi everyone, > > Thanks for raising this. I believe the Java implementation and the spec > are still in sync since for V1 we always write sc

[VOTE] Improve OpenAPI documentation around how NamespaceNotEmptyException is treated

00 on a bad request, thus the client should check the error type to know whether it received a *NamespaceNotEmptyException*. This vote will be open for at least 72 hours. [ ] +1 Improve the documentation in the OpenAPI spec [ ] +0 [ ] -1 I have concerns because ... Kind regards, Eduard

Re: [VOTE] Release Apache Iceberg 1.7.2 RC2

nclude this fix in order to make CTAS work with refreshing creds. Eduard On Wed, Mar 12, 2025 at 9:33 PM Kevin Liu wrote: > +1 (non-binding) > Verified signature, checksum, and license. Tested against JDK 17 > (`17.0.6-zulu`). > > Thanks for running the release! > > Best, >

Re: [VOTE] Release Apache Iceberg 1.7.2 RC2

+1 (binding) verified sigs/checksums/tests On Wed, Mar 12, 2025 at 7:48 AM Jean-Baptiste Onofré wrote: > +1 (non binding) > > Regards > JB > > On Wed, Mar 5, 2025 at 7:41 AM Jean-Baptiste Onofré > wrote: > > > > Hi everyone, > > > > I propose that we release the following RC as the official Ap

Re: [VOTE] Release Apache PyIceberg 0.9.0rc3

+1 (binding) checked signatures/checksums/license and ran tests via "make test-coverage". Thanks everyone On Mon, Mar 3, 2025 at 3:10 PM Sung Yun wrote: > Hi Drew, thank you very much for running the release! > > +1 non-binding: > > I've verified the signatures, the checksums and the licensing

[ANNOUNCE] Apache Iceberg release 1.8.1

I'm pleased to announce the release of Apache Iceberg 1.8.1! Apache Iceberg is an open table format for huge analytic datasets. Iceberg delivers high query performance for tables with tens of petabytes of data, along with atomic commits, concurrent writes, and SQL-compatible table evolution. This

Re: [VOTE] Release Apache Iceberg 1.8.1 RC1

>>>>> >>>>>>>> Does anyone know which change could introduce this? >>>>>>>> >>>>>>>> On Wed, Feb 26, 2025 at 5:16 AM Péter Váry < >>>>>>>> peter.vary.apa

Re: [VOTE] Java implementation notes around current-snapshot-id

+1 On Tue, Feb 25, 2025 at 7:31 AM Steven Wu wrote: > +1 > > On Mon, Feb 24, 2025 at 10:13 PM Péter Váry > wrote: > >> +1 >> >> On Tue, Feb 25, 2025, 04:16 Steve Zhang >> wrote: >> >>> +1 (nb) >>> Thanks, >>> Steve Zhang >>> >>> >>> >>> On Feb 24, 2025, at 6:32 PM, Renjie Liu wrote: >>> >>> +

[VOTE] Release Apache Iceberg 1.8.1 RC1

Hi Everyone, I propose that we release the following RC as the official Apache Iceberg 1.8.1 release. The commit ID is *9ce0fcf0af7becf25ad9fc996c3bad2afdcfd33d* * This corresponds to the tag: *apache-iceberg-1.8.1-rc1* * https://github.com/apache/iceberg/commits/apache-iceberg-1.8.1-rc1 * https:

Re: [VOTE] Release Apache Iceberg 1.8.1 RC0

d. On Thu, Feb 20, 2025 at 11:22 AM Yuya Ebihara < yuya.ebih...@starburstdata.com> wrote: > Hi, > > Thank you for preparing RC, Eduard. > > I tested 1.8.1 on Trino. The S3-compatible storage issue has been > resolved, but Unity catalog and tabulario/iceberg-rest:1.6.0

[VOTE] Release Apache Iceberg 1.8.1 RC0

Hi Everyone, I propose that we release the following RC as the official Apache Iceberg 1.8.1 release. The commit ID is 673192d9152a5532f2a84aa2fc815cfa16f7f203 * This corresponds to the tag: apache-iceberg-1.8.1-rc0 * https://github.com/apache/iceberg/commits/apache-iceberg-1.8.1-rc0 * https://gi

Re: [VOTE] Release Apache Iceberg 1.7.2 rc0

I think we should still do 1.7.2 and not leave it in a broken state. On Thu, Feb 20, 2025 at 7:56 AM Jean-Baptiste Onofré wrote: > Hi Hussein > > We were focusing on 1.8.x. > > Do you still need 1.7.2 or 1.8.0/1.8.1 is good enough for you ? > > Regards > JB > > On Wed, Feb 19, 2025 at 10:23 PM H

Re: [DISCUSS] Apache Iceberg 1.8.1 release

2025 at 11:24 AM Jean-Baptiste Onofré wrote: > Hi Eduard > > Thanks for volunteering for the 1.8.1 release. It makes sense to me. > I'm working on some Flink related updates, but for 1.9.0. > I will do a pass on GitHub Issues. > > Regards > JB > > On Wed, Feb 19,

[DISCUSS] Apache Iceberg 1.8.1 release

or 1.8.1 and the question to the community is, whether there's anything else that came up and should be included in 1.8.1. Otherwise I'll go ahead and do an RC by the end of this week. Thanks Eduard

Re: [VOTE] Add overwriteRequested to RegisterTableRequest in REST spec

+1 On Fri, Feb 14, 2025 at 12:57 AM Szehon Ho wrote: > +1 > > Thanks Steve! > Szehon > > On Thu, Feb 13, 2025 at 1:23 PM Yufei Gu wrote: > >> +1 (binding) >> Yufei >> >> >> On Thu, Feb 13, 2025 at 1:20 PM huaxin gao >> wrote: >> >>> +1 (non-binding) >>> >>> On Thu, Feb 13, 2025 at 11:51 AM Anu

Re: [ANNOUNCE] Apache Iceberg release 1.8.0

This is most likely caused by the additional checks that were added in https://github.com/apache/iceberg/pull/11756. On Thu, Feb 13, 2025 at 4:16 PM Gabor Kaszab wrote: > Hi, > > I think it's because of this patch: > https://github.com/apache/iceberg/commit/a2b8008da7bc26e03248a3560d1cc7e849

Re: [VOTE] Release Apache Iceberg 1.8.0 RC0

<https://github.com/apache/iceberg/issues/12236> for this. Eduard On Wed, Feb 12, 2025 at 6:42 PM Daniel Weeks wrote: > +1 (binding) > > Verified sigs/sums/license/build/test (Java 17) > > I also manually tested a number of cases with format v3 and DVs. > > -Dan &g

Re: [VOTE] Add RemoveSchemas update type to REST spec

+1 On Tue, Feb 11, 2025 at 10:40 AM Gabor Kaszab wrote: > Hi Iceberg Community, > > I'm working on removing the unused schemas from the table metadata when > running snapshot expiration. One part of this work is a change in REST spec > to add a new update type for removing schemas. > > I'd like

Re: [VOTE] Simplify multi-arg table metadata

+1 On Mon, Feb 10, 2025 at 7:40 AM Péter Váry wrote: > +1 > > On Mon, Feb 10, 2025, 03:44 Manu Zhang wrote: > >> +1 (non-binding) >> >> On Mon, Feb 10, 2025 at 10:25 AM roryqi wrote: >> >>> +1 >>> >>> xianjin 于2025年2月10日周一 10:02写道： >>> +1 (non-binding) On Mon, Feb 10, 2025 at 2

Re: [VOTE] Add Geometry and Geography types for V3

+1 On Sat, Feb 8, 2025 at 1:02 PM Fokko Driesprong wrote: > +1 > > Op za 8 feb 2025 om 08:08 schreef Péter Váry >: > >> +1 >> >> On Fri, Feb 7, 2025, 21:20 Kevin Liu wrote: >> >>> +1 (non-binding) >>> It's great to see support for more data types in both parquet and >>> Iceberg! >>> >>> Best,

Re: Welcome Huaxin Gao as a committer!

Congratulations Huaxin On Thu, Feb 6, 2025 at 2:40 PM Rodrigo Meneses wrote: > Congrats and best wishes !!! > > On Thu, Feb 6, 2025 at 5:04 AM Gidon Gershinsky wrote: > >> Congrats Huaxin! >> >> Cheers, Gidon >> >> >> On Thu, Feb 6, 2025 at 2:46 PM Tushar Choudhary < >> tushar.choudhary...@gmai

Re: [VOTE] Update partition stats spec for V3

+1 On Mon, Feb 3, 2025 at 8:33 PM Dongjoon Hyun wrote: > +1 for the proposal. > > Dongjoon > > > On Mon, Feb 3, 2025 at 2:35 PM ConradJam wrote: > > > > > +1 (non-binding) > > > > > > Steven Wu 于2025年2月3日周一 14:08写道： > > > > > >> +1 > > >> > > >> The spec change makes sense. left a question in

Re: [VOTE] Release Apache Iceberg 1.7.2 rc0

+1 (verified sigs/checksums/license/ran tests locally) On Tue, Jan 28, 2025 at 7:00 AM Yuya Ebihara wrote: > +1 (non-binding) > > Checked green CI on Trino https://github.com/trinodb/trino/pull/24814 > > BR, > Yuya > > On 2025/01/28 04:52:39 Cheng Pan wrote: > > +1 (non-binding) > > > > Pass int

Re: [VOTE] Add initial/write defaults to REST spec

+1 On Sat, Jan 25, 2025 at 9:35 AM Christian Thiel wrote: > +1 (non-binding) > > On Sat, 25 Jan 2025 at 07:34, Fokko Driesprong wrote: > >> +1 >> >> Op za 25 jan 2025 om 00:55 schreef Honah J. : >> >>> +1, thanks for driving this! >>> >>> Best Regards, >>> Honah >>> >>> On Fri, Jan 24, 2025 at

Re: [DISCUSS] Adding RemoveSchemasUpdate update type to REST spec

I agree that it makes sense to add this, so I'm +1 on this. On Mon, Jan 27, 2025 at 3:38 PM Jean-Baptiste Onofré wrote: > Hi Gabor > > Sorry for the late reply. > > It makes sense to me. Thanks ! > > Regards > JB > > On Wed, Jan 22, 2025 at 10:32 AM Gabor Kaszab > wrote: > > > > Hi Iceberg Comm

Re: [DISCUSS, VOTE] OpenAPI Metadata Update for EnableRowLineage

+1 On Thu, Jan 23, 2025 at 4:49 AM Honah J. wrote: > +1, thanks Russell! > > Best regards, > Honah > > On Wed, Jan 22, 2025 at 6:49 PM Renjie Liu > wrote: > >> +1, thanks Russell for driving this! >> >> On Thu, Jan 23, 2025 at 8:12 AM Russell Spitzer < >> russell.spit...@gmail.com> wrote: >> >>

Re: [VOTE] Document Snapshot Summary Optional Fields as Subsection of Appendix F in Spec

+1 On Wed, Jan 22, 2025 at 9:46 AM Fokko Driesprong wrote: > +1 > > Op wo 22 jan 2025 om 08:21 schreef Péter Váry >: > >> +1 >> >> On Wed, Jan 22, 2025, 06:06 huaxin gao wrote: >> >>> +1 (non-binding) >>> >>> On Tue, Jan 21, 2025 at 6:04 PM Manu Zhang >>> wrote: >>> +1 (non-binding)

Re: [VOTE] Deprecate IRC snapshot-id Field of SetStatisticsUpdate

+1 On Tue, Jan 21, 2025 at 5:34 PM Marc Cenac wrote: > +1 non-binding > > On Tue, Jan 21, 2025 at 8:19 AM Sung Yun wrote: > >> +1 non-binding >> >> Thanks for driving this Christian! >> >> On 2025/01/21 12:39:26 Russell Spitzer wrote: >> > +1 >> > >> > On Tue, Jan 21, 2025 at 4:34 AM Alex Dutra

Re: [Discuss][Vote] Spec Change - Add optional field added-rows to Snapshot for Row Lineage

+1 On Thu, Jan 16, 2025 at 7:53 AM huaxin gao wrote: > +1 (non-binding) > > On Wed, Jan 15, 2025 at 10:51 PM Gang Wu wrote: > >> +1 (non-binding) >> >> On Thu, Jan 16, 2025 at 2:30 PM Péter Váry >> wrote: >> >>> +1 >>> >>> Steven Wu ezt írta (időpont: 2025. jan. 16., Cs, >>> 0:46): >>> +

Re: [VOTE] Document Snapshot Summary Optional Fields as Appendix in Spec

+1 On Wed, Jan 15, 2025 at 1:20 AM rdb...@gmail.com wrote: > The content looks correct to me, but because this states a requirement > ("Metrics must be accurate if written") I would rather move this content > into the section on the snapshot summary instead of an appendix. > > On Tue, Jan 14, 20

Re: [VOTE] Drop Hive runtime

+1 On Wed, Dec 18, 2024 at 9:01 PM rdb...@gmail.com wrote: > The PR looks good to me. +1 > > On Tue, Dec 17, 2024 at 6:00 PM Manu Zhang > wrote: > >> Hi all, >> >> Thanks for sharing your ideas in the discussion of Hive support[1]. We >> have a consensus to drop Hive runtime and upgrade Hive me

Re: ​[discuss] Allow 200 responses for HEAD requests in REST API

sponse that the client needs to care about. Eduard On Tue, Dec 17, 2024 at 10:20 PM Yufei Gu wrote: > The distinction between 200 and 204 is subtle enough that I'm comfortable > using them interchangeably in this context. My main concern is that, if we > make this change, all clie

Re: 1.7.1 breaking change related to ADLS support

I agree with Fokko in that we should do a 1.7.2 release for people using ADLSFileIO On Tue, Dec 17, 2024 at 9:58 AM Fokko Driesprong wrote: > Thanks for raising this Alex, > > I suggest doing a 1.7.2 patch release since we don't want to leave the > 1.7.x version in a broken state for the ADLSFil

Re: New committer: Scott Donnelly

Congrats Scott! On Wed, Dec 11, 2024 at 7:35 AM roryqi wrote: > Congrats! > > Fenil Jain 于2024年12月11日周三 14:26写道： > >> Congratulations Scott! >> >> On Wed, Dec 11, 2024 at 8:56 AM Renjie Liu >> wrote: >> > >> > Hey everyone, >> > >> > The Project Management Committee (PMC) for Apache Iceberg ha

Re: New committer: Matt Topol

Congrats Matt! On Wed, Dec 11, 2024 at 6:41 AM Honah J. wrote: > Congratulations, Matt! > > On Tue, Dec 10, 2024 at 7:51 PM Fenil Jain wrote: > >> Congratulations Matt! >> >> On Tue, Dec 10, 2024 at 3:56 PM Fokko Driesprong >> wrote: >> > >> > Hey everyone, >> > >> > The Project Management Com

Re: [ANNOUNCE] Apache Iceberg release 1.7.1

Thanks Bryan and everyone else for making this release happen. On Tue, Dec 10, 2024 at 12:27 AM Yuya Ebihara wrote: > Thank you Brian! Trino project had waited for 1.7.1 that fixes namespace > regression. >

Re: [VOTE] Release Apache PyIceberg 0.8.1rc1

+1 (binding) but I've also had the same tests fail that Honah mentioned earlier (which are due to deprecated dependencies) On Wed, Dec 4, 2024 at 3:52 AM Sung Yun wrote: > +1 (non-binding) > > Checked signatures, checksums and validated license headers. > > Ran the coverage tests using python3.1

Re: [VOTE] Release Apache Iceberg 1.7.1 RC1

I actually verified everything (checksums, license checks, tests) last week but forgot to vote, sorry about that. Also thanks for running the release Bryan. +1 (binding) On Tue, Dec 3, 2024 at 8:37 AM Fokko Driesprong wrote: > Hey Bryan, > > Thanks for running the release! +1 binding from my en

Re: [DISCUSS] Apache Iceberg Summit 2025 - Selection Committee

Thanks for organizing this and I'd like to volunteer to help out where I can. On Wed, Nov 27, 2024 at 9:16 AM Christian Thiel wrote: > Hey JB, > > happy to help any way I can. Thanks for organizing this! > > Best, > Christian > > On 27. Nov 2024, at 07:52, Fokko Driesprong wrote: > > Hey JB, >

Re: [PROPOSAL] Store Iceberg build scans on ASF Develocity (ge.apache.org)

I think that's a good idea, so +1 from my side. On Mon, Nov 25, 2024 at 11:10 AM Jean-Baptiste Onofré wrote: > Hi folks, > > The ASF is hosting a Gradle Develocity instance where we can store our > build scans. > > It's hosted on https://ge.apache.org. > Several projects are using it (Apache Bea

Re: [VOTE][Go] Release Apache Iceberg Go v0.1.0 RC2

+1 (binding) verified checksum, signatures and tests Thanks Matt for doing the release On Thu, Nov 14, 2024 at 9:24 PM Kevin Liu wrote: > +1 (non-binding) > > Verified checksum, signature, tests > > I modified the verify_rc script to use artifacts from the apache dist > https://github.com/apac

Re: [DISCUSS] Iceberg 1.7.1 release

@Aihua I don't think #11324 is a good candidate to include for 1.7.1 as a patch release typically should only include bug fixes and not new features. We are planning to do a 1.8.0 in the next few weeks and so #11324 could be shipped with that. Thanks, Eduard On Fri, Nov 15, 2024 at 6:23 AM

Re: [DISCUSS] Spark 3.3 support?

+1 to deprecating and removing it On Wed, Nov 13, 2024 at 5:03 PM Anton Okolnychyi wrote: > What do folks think about our Spark 3.3 support? Spark 3.3.0 was released > in June, 2022. Given the 18 month maintenance period in Spark, it is no > longer maintained. The last release was in December, 2

Re: [VOTE][Go] Release Apache Iceberg Go v0.1.0 RC0

@Matt yes the licensing is a blocker unfortunately, so we should cancel the RC and start an RC1 vote once this is fixed. I should have properly voted in the earlier email, but will do it now. -1 (binding) due to the licensing On Tue, Nov 12, 2024 at 5:47 PM Jean-Baptiste Onofré wrote: > -1 (non

Re: [VOTE][Go] Release Apache Iceberg Go v0.1.0 RC0

I also ran into the same issues that Kevin pointed out earlier while verifying the release, but apart from that all tests passed. I think the LICENSE file needs to be updated as it contains Java-specific things, which can be seen in https://github.com/apache/iceberg-go/blob/main/LICENSE#L216-L315.

Re: Duplicates are getting inserted into Iceberg tables even after de-duplication

I do recall an issue where duplicate data/delete files where possible, but I'm not sure if that's the underlying cause in your case. The issue was fixed by #10007 and was shipped with Iceberg 1.6.0. On Thu, Nov 7, 2024 at 11:12 PM Lewis, William wrot

Re: [VOTE] Release Apache Iceberg 1.7.0 RC1

+1 (binding) Verified signature/checksum/license and build/test with JDK17 On Thu, Nov 7, 2024 at 3:11 AM Daniel Weeks wrote: > +1 (binding) > > Verified sigs/sums/license/build/test (Java 17) > > -Dan > > On Wed, Nov 6, 2024 at 3:23 PM Jack Ye wrote: > >> +1 (binding) >> >> - Verified signatu

Re: [VOTE] Release Apache Iceberg 1.7.0 RC0

+1 (binding) Verified signature/checksum/license and build/test with JDK17 On Mon, Nov 4, 2024 at 1:15 AM Honah J. wrote: > +1 (binding) > > Verified signature/checksum/license/build/test with JDK17 > > Best regards, > Honah > > On Sun, Nov 3, 2024 at 10:47 AM Cheng Pan wrote: > >> FYI, I jus

Re: [VOTE] Deletion Vectors in V3

+1 On Wed, Oct 30, 2024 at 7:28 AM Jean-Baptiste Onofré wrote: > +1 (non binding) > > Regards > JB > > On Tue, Oct 29, 2024 at 10:45 PM Anton Okolnychyi > wrote: > > > > Hi folks, > > > > We have been discussing the new layout for position deletes in V3 for a > while now. It seems the community

Re: [VOTE] Endpoint for refreshing vended credentials

t 10:50 AM John Zhuge wrote: >> >> +1 (non-binding) >> >> John Zhuge >> >> >> On Tue, Oct 22, 2024 at 9:45 AM Jack Ye wrote: >> >> +1 (binding) >> >> Best, >> Jack Ye >> >> On Tue, Oct 22, 2024 at 9:32 AM Dmitr

Re: [PROPOSAL] Refactore use of Guava Lists.*

e diamond syntax and is it worth updating the entire codebase? to loosen the Lists/Maps/... enforcement in spotless) FYI this is being enforced by checkstyle and was first introduced by https://github.com/apache/iceberg/pull/3689 in order to have a consistent style around collection instantiation

Re: [VOTE] Endpoint for refreshing vended credentials

n what specific credentials a client wants to receive from the server. Thanks, Eduard On Mon, Oct 21, 2024 at 6:36 PM Dmitri Bourlatchkov wrote: > -0 (non-binding) > > If multiple credentials are vended for a table (which is allowed) the > current API requires all credentials to be

[VOTE] Endpoint for refreshing vended credentials

urs [ ] +1, commit the proposed spec changes [ ] -0 [ ] -1, do not make these changes because . . . Thanks everyone, Eduard

Re: [VOTE] Standardize vended credentials in OpenAPI spec

With 8 +1 votes the VOTE passed. Thanks everyone On Fri, Oct 18, 2024 at 12:34 AM Jack Ye wrote: > +1 (binding) > > Best, > Jack Ye > > On Thu, Oct 17, 2024 at 3:05 PM Dmitri Bourlatchkov > wrote: > >> +1 (non-binding) >> >> Cheers, >> Dmit

Re: [DISCUSS] Remove iceberg-pig module ?

+1 for marking the project deprecated (in 1.7.0) and dropping it in the next release (1.8.0) On Thu, Oct 17, 2024 at 4:36 PM Russell Spitzer wrote: > +1 (oink) > > If anyone really cares please chime in but seriously we should drop it > > On Thu, Oct 17, 2024 at 8:07 AM Jean-Baptiste Onofré > w

[VOTE] Standardize vended credentials in OpenAPI spec

forward. Please vote in the next 72 hours [ ] +1, commit the proposed spec changes [ ] -0 [ ] -1, do not make these changes because . . . Thanks everyone, Eduard

Re: [DISCUSS] REST: Standardize vended credentials in Spec

der to get this in. Thanks everyone On Fri, Oct 11, 2024 at 3:11 PM Dmitri Bourlatchkov wrote: > Hi Eduard, > > The latest REST spec change PR LGTM overall. > > I think it does make sense to avoid putting vendor-specific credential > properties into the REST spec itself.

Re: [DISCUSS] REST: Refreshing vended credentials

ing to document storage-specific configuration with #10576 <https://github.com/apache/iceberg/pull/10576>, so that should generally solve this issue and servers/clients should know what to send/use. Eduard On Mon, Oct 14, 2024 at 7:34 PM Yufei Gu wrote: > Hi Eduard, > > Thanks

Re: [VOTE] Table V3 Spec: Row Lineage

I left a few comments on the proposal but I'm overall +1 on the proposal On Thu, Oct 10, 2024 at 12:08 PM Jean-Baptiste Onofré wrote: > +1 > > I did a review on the proposal and it looks good to me. > > Regards > JB > > On Tue, Oct 8, 2024 at 3:55 PM Russell Spitzer > wrote: > > > > Hi Y'all! >

Re: [PROPOSAL] Partially Loading Metadata - LoadTable V2

tadata-log / snapshot-log / schemas*. Might be worth checking how much we could gain by using a lazy table metadata supplier in this scenario, as that would reduce the required complexity. Thanks, Eduard On Thu, Oct 10, 2024 at 2:05 AM Haizhou Zhao wrote: > Hello Dev List, > > >

[DISCUSS] REST: Refreshing vended credentials

apache.org/thread/jmklpnywnghg7qwmwr14zj2k6tnxmdo4. Thanks, Eduard

Re: [Discuss] Replace Hadoop Catalog Examples with JDBC Catalog in Documentation

I would prefer to advocate for the REST catalog in those examples/docs (similar to how the Spark quickstart example uses the REST catalog). The docs could then refer to the quickstart example to indicate what's required in terms of services to be start

  1   2   3   >