Nessie now supports two types of requests: Nessie API v1/2 and Iceberg REST API.
The author of a write operation is inferred from the authentication type. If I remember correctly, with the Nessie APIs, it's possible to define metadata related to the user performing the write operation.
I'm wondering if it would be possible to support, for both APIs, the ability to define and override the message author by setting an HTTP Header (X-Nessie-Author?)
Expected Use Cases
There are cases where there's a generic authentication for an organization, but multiple users within the organization can modify the data catalog.
By standardizing a header compatible with both Nessie API v1/2 and Iceberg REST API, it would become easier to propagate information about the user performing the modification operation in a way that is agnostic to the type of API implementation the system is using.
This solution should also be compatible with pyiceberg. At the init time we can specify the headers the library needs to send to the server.
Description
Nessie now supports two types of requests: Nessie API v1/2 and Iceberg REST API. The author of a write operation is inferred from the authentication type. If I remember correctly, with the Nessie APIs, it's possible to define metadata related to the user performing the write operation.
I'm wondering if it would be possible to support, for both APIs, the ability to define and override the message author by setting an HTTP Header (
X-Nessie-Author
?)Expected Use Cases
There are cases where there's a generic authentication for an organization, but multiple users within the organization can modify the data catalog.
By standardizing a header compatible with both Nessie API v1/2 and Iceberg REST API, it would become easier to propagate information about the user performing the modification operation in a way that is agnostic to the type of API implementation the system is using.
This solution should also be compatible with
pyiceberg
. At the init time we can specify the headers the library needs to send to the server.Requested Changes in public API
No response