mansehajsingh commented on PR #1037:
URL: https://github.com/apache/polaris/pull/1037#issuecomment-2752931562

   I have updated the PR to address a new solution that would address the 
concerns about consistency:
   
   We can use the hash of the metadata file location as the value for the ETag. 
This works well because it is available in the `TableMetadata` in the 
`LoadTableResponse` returned by the `CatalogHandlers` meaning that it will 
always be consistent with the metadata when we generate the ETag. Also, it is 
present on the `IcebergTableLikeEntity`, so we can use it without having to go 
load the table metadata from storage to do comparisons, which would remove the 
performance benefit. We find the SHA256 OF the metadata file location so that a 
client cannot try to abuse the ETag header to fetch the metadata file location.
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to