Re: [DISCUSS] Rename iceberg repo to iceberg-java ?

OK, thanks guys for your feedback. It was a more "open question" to give more "consistency" (like other projects did, Arrow, Parquet, etc). But definitely not strongly required :) Let's skip this one for now. Regards JB On Fri, Mar 14, 2025 at 7:29 PM Daniel Weeks wrote: > > I'm not in favor o

[VOTE] Improve OpenAPI documentation around how NamespaceNotEmptyException is treated

Hey everyone, I'd like to hold a quick VOTE on #12518 that improves the documentation around how *NamespaceNotEmptyException* is treated when a non-empty namespace is deleted. In such a case we do return a 400 and we also return a 400 on a bad request

Re: [DISCUSS] Rename iceberg repo to iceberg-java ?

I agree with Russell that the spec should remain language-agnostic. However, for the Java client (and other integrations implemented in Java), +1 for moving them to a new repository. Alternatively, we could rename the current repository and relocate the spec to a new repository under the existing n

Re: cleanExpiredMetadata in RemoveSnapshots

I don't think it is necessary to either make cleanup the default or to expose the flag in Spark or other engines. Right now, catalogs are taking on a lot more responsibility for things like snapshot expiration, orphan file cleanup, and schema or partition spec removal. Ideally, those are tasks tha

Re: cleanExpiredMetadata in RemoveSnapshots

I would be hesitant to turn on any new feature by default. Especially for Spark compaction which is widely used in production. +1 for providing a way for the users to enable the feature manually Gabor Kaszab ezt írta (időpont: 2025. márc. 14., P, 12:19): > Hi Iceberg Community, > > There were r