You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@iceberg.apache.org by GitBox <gi...@apache.org> on 2022/09/05 11:52:28 UTC

[GitHub] [iceberg] Shane-Yu commented on issue #5671: The upsert mode can query the historical version of the data under certain conditions

Shane-Yu commented on issue #5671:
URL: https://github.com/apache/iceberg/issues/5671#issuecomment-1236900418

   > Do you mean: it should see empty row set when execute the following SQL ?
   > 
   > ```sql
   > hive (iceberg_yx)> select * from upsert_update_time_test where update_time <= '2022-08-26 15:45:00';
   > OK
   > upsert_update_time_test.id upsert_update_time_test.data upsert_update_time_test.update_time
   > 1 101 2022-08-26 15:44:50
   > ```
   > 
   > I'm not quite sure that whether your input stream `rowDataStream` will really transform the `U, 1, .. ` record as an `UPDATE` event , you can try to confirm this.
   
   
   Yeah, the result should be empty. This seems to be the problem of this PR https://github.com/apache/iceberg/pull/4316#issuecomment-1066097462, but this phenomenon only occurs for parquet files and 'write.metadata.metrics.default'='full'. When putting 'write.metadata.metrics.default'='count', the problem goes away.
   


-- 
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