The very first call to a REST Catalog is to fetch a CatalogConfig object via /v1/config. This may include additional properties needed for further REST Catalog API calls (Iceberg handles this at internally in org.apache.iceberg.rest.RESTSessionCatalog). The additional properties may also contain credentials to access a warehouse, like S3. This sort of access control is implementation dependant, but this is the model that Polaris REST Catalog uses.
Iceberg exposes the full set of properties after initialization via org.apache.iceberg.rest.RESTCatalog#properties.
This PR passes along the full set of properties for REST Catalogs to DataInstructionsProviderPlugin.
This issue was auto-generated
PR: https://github.com/deephaven/deephaven-core/pull/6191 Author: devinrsmith
Original PR Body
The very first call to a REST Catalog is to fetch a CatalogConfig object via /v1/config. This may include additional properties needed for further REST Catalog API calls (Iceberg handles this at internally in
org.apache.iceberg.rest.RESTSessionCatalog). The additional properties may also contain credentials to access a warehouse, like S3. This sort of access control is implementation dependant, but this is the model that Polaris REST Catalog uses.Iceberg exposes the full set of properties after initialization via
org.apache.iceberg.rest.RESTCatalog#properties.This PR passes along the full set of properties for REST Catalogs to
DataInstructionsProviderPlugin.