OAC - BigQuery Connector - Support multiple Keys

RichardReader

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of): Intercontinental Hotels Group

Description (Required):

Currently DV BigQuery connection only supports 1 json key (although this is broken).

The retrieval of the metadata when creating a dataset will only work correctly for the first key used on an OAC instance.

Every key after that will retrieve the incorrect metadata.

If the first key used on the OAC instance has additional access in OAC this WILL NOT be updated in the OAC metadata.

I believe this to be broken, however on the service request below I was told it is working as designed, hence this enhancement request.

Use Case and Business Need (Required):

As there is no option to use local BigQuery accounts, it is unrealistic to expect an organization to use a single key for access in DV. At the moment this is unusable for our organization.

EDIT: Different functions / teams / users will have their own PK with a specific set of access/rights in BigQuery. Multiple and different PKs need to retrieve the correct metadata to enable the use of this connector. BigQuery will be a primary data source for many teams and without support would mean OAC is no longer an option.

'You create an initial connection to BigQuery supplying the Service Account PK. You then create a subsequent connection using a new key. The 2nd connection is not retrieving the right metadata'

Enhancement Request / Service Request:

SR 3-26571728191

Alan Lee - Oracle-Oracle

Can you clarify the use case? i.e. You create an initial connection to BigQuery supplying the Service Account PK. You then create a subsequent connection using a new key. The 2nd connection is not retrieving the right metadata?

RichardReader

Hi, yes that is correct. After raising an SR regarding this, I was told that OAC only supports a single key. Hence the request to add support for multiple.

Also note, the metadata retrieval for a single key does not seem to refresh, if the PK access changes in BigQuery.