henrib opened a new pull request, #6936:
URL: https://github.com/apache/hive/pull/6936

   ### What changes were proposed in this pull request?
   - New setting `metastore.iceberg.catalog.client-supplied-owner.enabled` 
(default `false`).
     When disabled, the REST catalog records the authenticated caller as owner 
of new
     tables and views. Embedded `HiveCatalog` keeps its current behaviour
     (`iceberg.hive.client-supplied-owner.enabled`, default `true`).
   - `hive.metastore.table.owner`, `Authorized` and 
`hive.metastore.view.authorized` are
     treated as HMS-managed view properties: they are not copied into HMS 
parameters, and
     the REST catalog drops them from view create/update requests.
   - REST view responses report the owner and `Authorized` state recorded in 
HMS for the
     returned metadata version.
   - `HiveRESTCatalogClient` maps `hive.metastore.view.authorized` back to the 
`Authorized`
     view parameter; `MetastoreUtil` keeps the HMS-recorded owner when 
converting a view.
   
   ### Why are the changes needed?
   Keeps owner and view authorization state consistent with what HMS records. 
See HIVE-29992.
   
   ### Does this PR introduce _any_ user-facing change?
   Yes. With the default configuration, the Iceberg REST catalog sets the owner 
of new
   tables and views to the authenticated caller instead of a client-provided 
value. The
   previous behaviour can be restored with
   `metastore.iceberg.catalog.client-supplied-owner.enabled=true`.
   
   ### How was this patch tested?
   New and updated unit tests: `TestRESTViewDeferredAuthorization`, 
`TestIcebergAuthorizer`,
   `TestIcebergViewSupport`, `TestHiveHadoopUtil`; new itest
   `TestHiveRESTCatalogClientViewAuthorization`.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


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