Re: Update existing partition spec

Hi Devs, I had the same problem. and i commit a PR, try to fix it. https://github.com/apache/iceberg/pull/2691

Re: Update existing partition spec

Hi Laszlo, As Jack mentioned, this behavior happened to v1 format. If you want to stay with v1 format, a short term workaround is to add back this field with a different name, e.g. table.updateSpec().addField("ts_month_new", month("ts")).commit(); or rename the field before deleting it table.u

Re: Update existing partition spec

Hi Laszlo, I think this is expected behavior of format v1, where a dropped partition column is actually converted to a null transform instead of being actually dropped. This is because the partition spec is not versioned in v1. See https://github.com/apache/iceberg/blob/efaad975fc9bbeaa27392b3332

Update existing partition spec

Hi Iceberg Devs, I'm using the Iceberg API to drop/add partition transforms, but recently I've run into an issue. When I try to add a new partition that previously existed, but it was already dropped I get *Cannot use partition name more than once *error message. Here is what I'm doing: table.up