Tom-Newton opened a new issue, #38330:
URL: https://github.com/apache/arrow/issues/38330

   ### Describe the enhancement requested
   
   https://github.com/apache/arrow/pull/38269 implements Azure file reads 
including fetching file metadata. The implementation in that PR 
[chose](https://github.com/apache/arrow/pull/38269#discussion_r1360324803) to 
just return the user defined metadata on the blob as it was in 
https://github.com/apache/arrow/pull/12914. 
   
   However this is not quite right. I think really we want to return the 
information in the 
[BlobPropeties](https://github.com/Azure/azure-sdk-for-cpp/blob/1e013e5fe90d742b9b0ef2210e1cca1e638c18ec/sdk/storage/azure-storage-blobs/inc/azure/storage/blobs/rest_client.hpp#L1761)
 which contains more system level information like last modified time, etc. 
Looking at the [GCS 
filessytem](https://github.com/apache/arrow/blob/08e5206a69ec1b5e8bb13fad0e14c22510cdb877/cpp/src/arrow/filesystem/gcsfs_test.cc#L1073-L1133)
 it contains information fairly similar to  what is in 
[BlobPropeties](https://github.com/Azure/azure-sdk-for-cpp/blob/1e013e5fe90d742b9b0ef2210e1cca1e638c18ec/sdk/storage/azure-storage-blobs/inc/azure/storage/blobs/rest_client.hpp#L1761)
   
   Probably this will require a big function to map all the fields of 
[BlobPropeties](https://github.com/Azure/azure-sdk-for-cpp/blob/1e013e5fe90d742b9b0ef2210e1cca1e638c18ec/sdk/storage/azure-storage-blobs/inc/azure/storage/blobs/rest_client.hpp#L1761)
 to `KeyValueMetadata` and a corresponding update to the 
`OpenInputStreamReadMetadata` test. I thought it would be best to do this in a 
separate PR in the interest of keeping PRs small and easily re-viewable. 
   
   Related Issues:
   
   https://github.com/apache/arrow/issues/37511 (is caused by)
   
   ### Component(s)
   
   C++


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