collado-mike opened a new pull request, #193:
URL: https://github.com/apache/polaris/pull/193

   # Description
   
   Custom `write.data.path` and `write.metadata.path` are currently blocked, 
preventing users from following the guidelines in 
https://iceberg.apache.org/docs/1.5.1/aws/#object-store-file-layout . This 
updates the blocking to allow for customized write paths with the existing 
`ALLOW_UNSTRUCTURED_TABLE_LOCATION` configuration flag. This also adds a test 
using the object store location provider feature.
   
   Fixes https://github.com/apache/polaris/issues/113
   
   ## Type of change
   
   Please delete options that are not relevant.
   
   - [ ] Bug fix (non-breaking change which fixes an issue)
   - [X] New feature (non-breaking change which adds functionality)
   - [ ] Breaking change (fix or feature that would cause existing 
functionality to not work as expected)
   - [ ] This change requires a documentation update
   
   # How Has This Been Tested?
   
   New pytest for S3
   
   - [ ] Test A
   - [ ] Test B
   
   **Test Configuration**:
   * Firmware version:
   * Hardware:
   * Toolchain:
   * SDK:
   
   # Checklist:
   
   Please delete options that are not relevant.
   
   - [ ] I have performed a self-review of my code
   - [ ] I have commented my code, particularly in hard-to-understand areas
   - [ ] I have made corresponding changes to the documentation
   - [ ] My changes generate no new warnings
   - [ ] I have added tests that prove my fix is effective or that my feature 
works
   - [ ] New and existing unit tests pass locally with my changes
   - [ ] Any dependent changes have been merged and published in downstream 
modules
   - [ ] If adding new functionality, I have discussed my implementation with 
the community using the linked GitHub issue
   


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