[GitHub] [iceberg] ajantha-bhat commented on a diff in pull request #6771: Docs: Document that partitions metadata table might show 'old' partitions

["ajantha-bhat (via GitHub)" <gi...@apache.org>]

ajantha-bhat commented on code in PR #6771:
URL: https://github.com/apache/iceberg/pull/6771#discussion_r1100063008


##########
docs/spark-queries.md:
##########
@@ -346,6 +346,9 @@ SELECT * FROM prod.db.table.partitions;
 Note:
 For unpartitioned tables, the partitions table will contain only the record_count and file_count columns.
 
+Note2:
+The output of the above query might differ between having copy-on-write or merge-on-read strategies. E.g. delete files with MOR strategy aren't applyied when producing the content of the partitions metadata table. As a result if you have renamed a partition (by updating the value of a partition column) then you would see both the 'old' and the 'new' one until you do a rewrite of delete/data files.

Review Comment:
   ```suggestion
   The output of the above query might differ between having copy-on-write or merge-on-read strategies. For example, delete files with merge-on-read strategy aren't applied when producing the content of the partitions metadata table. As a result, if the table has renamed the partitions (by updating the value of a partition column), then the query output would contain both the 'old' and the 'new' partition values until rewrite data files (with delete files) is executed. 
   ```



-- 
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-unsubscribe@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@iceberg.apache.org
For additional commands, e-mail: issues-help@iceberg.apache.org