rdblue commented on issue #280: Add persistent IDs to partition fields
URL:
https://github.com/apache/incubator-iceberg/issues/280#issuecomment-526704926
@manishmalhotrawork, one strange thing about your test is that `data_bucket`
has a different ID. It should continue to use id 1000
rdblue commented on issue #280: Add persistent IDs to partition fields
URL:
https://github.com/apache/incubator-iceberg/issues/280#issuecomment-525451795
> And also as TableMetadata knows how many fields are in partition, so can
maintain the nextIDValue as well.
The next partition
rdblue commented on issue #280: Add persistent IDs to partition fields
URL:
https://github.com/apache/incubator-iceberg/issues/280#issuecomment-524938283
@manishmalhotrawork, those IDs have different contexts. The source ID in a
partition field is the ID of the source data column in the
rdblue commented on issue #280: Add persistent IDs to partition fields
URL:
https://github.com/apache/incubator-iceberg/issues/280#issuecomment-524579846
@manishmalhotrawork, we need to keep track of IDs that have been assigned to
partition fields in a table and reuse them when partition
rdblue commented on issue #280: Add persistent IDs to partition fields
URL:
https://github.com/apache/incubator-iceberg/issues/280#issuecomment-515096818
@timmylicheng, sorry for the confusion. The partition spec ID and the IDs
I'm talking about here aren't the same thing. Partition specs
rdblue commented on issue #280: Add persistent IDs to partition fields
URL:
https://github.com/apache/incubator-iceberg/issues/280#issuecomment-514712278
Yes. If a table has multiple partition specs, it will probably have multiple
manifests, each written with one of those specs.
