Time-based partitioning on long column type

Hi all, We have source data with a timestamp field in LONG type to land in an Iceberg table. We want to partition the table with the timestamp field such that we can query recent data more efficiently. However, LONG is not supported as the source type of time-based transform (hour, day, etc) I fi

Re: Materialized view integration with REST spec

Sounds good regarding voting to confirm on the direction. We can continue to try to reach consensus. I believe having common understanding about what we are evaluating (or building consensus towards) is crucial to have productive discussions. I see Jan has added more comments to the doc this mornin

Re: Materialized view integration with REST spec

I don't think we're in a position to open a vote (or maybe there's a misunderstanding of what the vote is set out to achieve). We need to continue the discussion until there is a general consensus on the direction we want to go (not on what options are available). The vote is a confirmation of th

[VOTE] Release Apache PyIceberg 0.6.1rc1

Hi Everyone, I propose that we release the following RC as the official PyIceberg 0.6.1 release. This is a patch release due to a serious bug that has been found . Smaller bugs also have been backported

Re: [PROPOSAL] New REST Catalog Spec

Hi Ajantha Thanks for your comments in the doc ! I will address your comments. Regards JB On Tue, Apr 2, 2024 at 10:56 AM Ajantha Bhat wrote: > > Nice proposal. > Thanks for working on it. > Just finished going through the doc and added some inputs. > > I believe that through further discussion

Re: [PROPOSAL] New REST Catalog Spec

Nice proposal. Thanks for working on it. Just finished going through the doc and added some inputs. I believe that through further discussion, we can establish a robust standard for the catalog specification 👍 - Ajantha On Mon, Apr 1, 2024 at 8:07 PM Jean-Baptiste Onofré wrote: > Hi folks, > >