rsion 2 in order to use any of
>>>> the metadata changes we are making” If I understand correctly, for exist
>>>> iceberg table in v1, we have to run some CLI/script to rewrite the
>>>> metadata.
>>>>
>>>>
>>>>
>>>> “N
a V2 reader on
>> a V1 table.
>>
>>
>>
>> However, if a table has been written in V1, we want to save it as V2. I
>> expect only metadata data will be rewritten into V2 and V1 metadata will be
>> vacuumed upon V2 success.
>>
>>
>>
&
numbers and the proposed inheritance scheme
>>> to v2, along with tests to ensure that v1 is written without sequence
>>> numbers and that when reading v1 metadata, the sequence numbers are all 0.”
>>> To me, this means V2 reader should be able to read V1 table metadata.
ave it as V2. I
>> expect only metadata data will be rewritten into V2 and V1 metadata will be
>> vacuumed upon V2 success.
>>
>>
>>
>> Is my understanding correct?
>>
>>
>>
>> Thanks!
>>
>>
>>
>> Miao
>>
&
understanding correct?
>
>
>
> Thanks!
>
>
>
> Miao
>
> From: Ryan Blue
> Reply-To: "dev@iceberg.apache.org <mailto:dev@iceberg.apache.org>"
> mailto:dev@iceberg.apache.org>>, "rb...@netflix.com
> <mailto:rb...@netflix
will be
> vacuumed upon V2 success.
>
>
>
> Is my understanding correct?
>
>
>
> Thanks!
>
>
>
> Miao
>
> *From: *Ryan Blue
> *Reply-To: *"dev@iceberg.apache.org" , "
> rb...@netflix.com"
> *Date: *Tuesday, May 5, 2020 at 5:
apache.org" ,
"rb...@netflix.com"
Date: Tuesday, May 5, 2020 at 5:03 PM
To: Iceberg Dev List
Subject: [DISCUSS] Changes for row-level deletes
Hi, everyone,
I know several people that are planning to attend the sync tomorrow are
interested in the row-level delete work, so I wa
Besides I'd like to share some work in my flink team, hope it will be
helpful for you.
We have customers who want to try the flink+iceberg to build their business
data lake, the classic scenarios are: 1. streaming click events into
iceberg and analyze by other olap engines ; 2. streaming CDC even
The two-phrase approach sounds good to me. the precondition is we have
limited number of delete files so that memory can hold all of them, we will
have the compaction service to reduce the delete files so it seems not a
problem.
Hi, everyone,
I know several people that are planning to attend the sync tomorrow are
interested in the row-level delete work, so I wanted to share some of the
progress and my current thinking ahead of time.
The codebase now supports a new version number, 2. Tables must be manually
upgraded to ve
10 matches
Mail list logo
