markhoerth opened a new issue, #14473:
URL: https://github.com/apache/gravitino/issues/14473

   ### Version
   
   main branch
   
   ### Describe what's wrong
   
   The Iceberg REST catalog writes an `owner` property, set to the 
authenticated creator, into every namespace and table it creates 
(`IcebergNamespaceOperationExecutor.createNamespace`, 
`IcebergTableOperationExecutor.createTable`). `owner` is the conventional 
Iceberg and Hive owner key that engines display. Nothing keeps it in step with 
Gravitino ownership:
   
   - After `PUT /api/metalakes/{m}/owners/table/{t}` moves ownership, the IRC 
and the Gravitino schema and table `properties` still name the creator, while 
the owner API names the new owner.
   - Any user who can change properties through the IRC can set `owner` to any 
name with `set-properties` on a table or `POST .../properties` on a namespace.
   
   ### Error message and/or stacktrace
   
   ```
   PUT  /api/metalakes/m/owners/table/c.ns.t {"name":"writer","type":"USER"}   
200
   GET  /iceberg/v1/c/namespaces/ns/tables/t   metadata.properties.owner = 
"admin"
   POST /iceberg/v1/c/namespaces/ns/tables/t 
{"updates":[{"action":"set-properties","updates":{"owner":"reader"}}]}   200
   GET  /api/metalakes/m/owners/table/c.ns.t   owner = writer, 
table.properties.owner = "reader"
   ```
   
   ### How to reproduce
   
   1. Create a namespace and table through the IRC as `admin`.
   2. Transfer ownership of both to another user through the Gravitino API, 
then load them through the IRC.
   3. Set `owner` through IRC property updates on the table and the namespace.
   
   ### Additional context
   
   Expected: one answer for an object's owner. The property follows Gravitino 
ownership and cannot be changed through IRC property updates.


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