Kimura-S2001 opened a new issue, #15270:
URL: https://github.com/apache/iceberg/issues/15270

   ### Feature Request / Improvement
   
   ### Describe the improvement
   
   When creating a view with a custom metadata location using 
`WRITE_METADATA_LOCATION`,
   the current behavior is confusing and not clearly documented.
   
   This is not a critical bug, but it is difficult for users to understand:
   - whether specifying a custom metadata location for views is supported
   - what the expected behavior should be
   - whether the resulting behavior is intentional or a limitation
   
   As a result, users may assume they are misconfiguring something or 
encountering a hidden bug.
   
   
   ---
   
   ### Background / Motivation
   
   This issue is based on the investigation of the following question:
   
   - https://github.com/apache/iceberg/issues/15103
   
   In that question, it was unclear whether the observed behavior was expected.
   To clarify this, I performed a verification to isolate the conditions and 
reproduce the behavior consistently.
   
   
   ---
   
   ### What I verified
   
   I verified the behavior by explicitly creating a view with a custom metadata 
location.
   
   #### Setup
   - Apache Iceberg: 1.10.x
   - Catalog: Hive catalog
   - Java: 17
   - Environment: local setup using Docker
   
   #### Configuration
   ```java
   .withProperty(ViewProperties.WRITE_METADATA_LOCATION, customLocation)
   .withLocation(location)
   .create();
   
   
   ### Query engine
   
   None
   
   ### Willingness to contribute
   
   - [ ] I can contribute this improvement/feature independently
   - [ ] I would be willing to contribute this improvement/feature with 
guidance from the Iceberg community
   - [ ] I cannot contribute this improvement/feature at this time


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to