Yufei Gu

It'd be better to provide more details to get help. Something like a full stack trace, what did you do to trigger the issue.

Not aware of the reason of the original decision, but replacing makes more sense to me. The lingering properties will potentially mess up the behavior, and surprise users.

Thanks @chenjunjiedada for bringing it up. It is good to have the statistic(min seq. number) for delete files, which will make rewrite a bit easier. I don't have much context...

Thanks @anuragmantri for filing the PR and updating the design doc. It is great that there is no spec change in the latest design.

> For table metadata files, there is only an external location for Hadoop tables. Otherwise, the table location must come from the table's metadata.json file. That makes it difficult to...

> Is there an easier way to create a full working replica of an Iceberg table where we do not use any files/data from the original table and the 2...

@pvary, yes, the relative path approach looks more elegant than the metadata rebuild one. As I mentioned, it is close to the ideal case, which doesn't rewrite the metadata files....

Hi @wypoon, thanks for the PR. I don't see a strong reason to expose the threshold to users. Instead, it's better to hide it from users. Here are reasons: 1....

@wypoon, we can put the new test case in the class like `TestPositionFilter`, in that case, it is easier to modify the threshold, and we don't have to touch any...

Hi @wypoon, sorry I may not be clear in my last comment. Let me explain a bit more. 1. No matter whether the pos deletes are streamed or not. Most...