You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have setup a REST catalog using Hive Metastore catalog. When a spark pipeline run and connect to the REST Catalog, the user (UGI) who ran the pipeline doesn't get reflected in the Hive Metastore, it takes the docker container username (iceberg).
How possible could be to send this information? Could it be common between catalogs? Sending this information to Hive Metastore will it be similar to Glue Catalog? Or does it need custom code for each extension?
If I get some advice, I could try to help 👍
The text was updated successfully, but these errors were encountered:
Hey @javsanbel2, Identity propagation is different between REST and HMS, so I'm not sure we want to just push the HMS approach into the REST spec.
With REST, implementations typically use the AUTHORIZATION header to provide/interpret identity (e.g. OAuth/OIDC token). This image is a simple implementation and it's possible you could use something like basic header to provide username information, but other than that, it would require a more complicated implementation.
Just adding fields to pass through leads to non-standard solutions, so I don't think extending the HMS approach is a good idea here.
Hello all,
I have setup a REST catalog using Hive Metastore catalog. When a spark pipeline run and connect to the REST Catalog, the user (UGI) who ran the pipeline doesn't get reflected in the Hive Metastore, it takes the docker container username (iceberg).
How possible could be to send this information? Could it be common between catalogs? Sending this information to Hive Metastore will it be similar to Glue Catalog? Or does it need custom code for each extension?
If I get some advice, I could try to help 👍
The text was updated successfully, but these errors were encountered: