rdsarvar commented on PR #11368: URL: https://github.com/apache/iceberg/pull/11368#issuecomment-2457637165
> Thanks @rdsarvar , the part I'm a bit confused about is why we need a new `useSpec` API. I think the use case you described could be solved by adding a new spec, without setting it as the default (which we recently added support for). Then the compaction could be performed using the spec ID of that added spec. I was looking at the public APIs and there doesn't seem to be an available method that would allow me to parse and directly add a new partition spec. Am I missing an API that would simplify this? If I were to use the `updateSpec` functionality and set `addNonDefaultSpec` then I'd need to iteratively removeField + addField over the partition spec provided in the action. My thinking was that as part of transactions + the provided methods in the `Table` interface we'd still need to provide a form of `addSpec` functionality as there's only `updateSpec` right now. Let me know if that makes sense or if I'm missing something 😄 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
