Yes, I have just a try to edit v1.metadata.json, but it failed because of
.v1.metadata.json.crc, then I back the v1.metadata.json, but
.v1.metadata.json.crc still fails
So are there security risks ? If xxx.metadata.json by someone
| |
liubo07199
|
|
liubo07...@hellobike.com
|
签名由网易邮箱大师定制
On
You edited the v1.metadata.json to support iceberg format v2 ? That's not
the correct way to use iceberg format v2. let's discuss this issue in the
latest email .
On Sat, Dec 26, 2020 at 7:01 PM 1 wrote:
> Hi, all:
>
>I vim the v1.metadata.json, so old .v1.metadata.json.crc is not
>
> you can apply this patch in your own repository
The patch is : https://github.com/apache/iceberg/pull/1978
On Mon, Dec 28, 2020 at 10:32 AM OpenInx wrote:
> Hi liubo07199
>
> Thanks for testing the iceberg row-level delete, I skimmed the code, it
> seems you were trying the equality-delete f
Hi liubo07199
Thanks for testing the iceberg row-level delete, I skimmed the code, it
seems you were trying the equality-delete feature. For iceberg users, I
think we don't have to write those iceberg internal codes to get this work,
this isn't friendly for users. Instead, we usually use the
e
