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
OMD 1.6.3
I have two GCP projects:
project_main
project_semantic
I have a service account on project main with cross-project access to project semantic.
When I set-up a BQ connection with multiple projects – only the first project works.
I have done two ingestions with two projects. Test connections work in both cases. Using credentials path.
However
Setup 1: I have added project main first – it was ingested, but not the project semantic.
Setup 2: I have added project semantic first – it was ingested, but not the project main.
It is clear that the SA has access in both projects to collect the metadata, but somehow only the first project is ingested in any of the set-up.
Affected module
UI 1.6.3
Describe the bug
As here https://openmetadata.slack.com/archives/C02B6955S4S/p1740073354194179?thread_ts=1740073354.194179&cid=C02B6955S4S
To Reproduce
OMD 1.6.3
I have two GCP projects:
project_main
project_semantic
I have a service account on project main with cross-project access to project semantic.
When I set-up a BQ connection with multiple projects – only the first project works.
I have done two ingestions with two projects. Test connections work in both cases. Using credentials path.
However
Setup 1: I have added project main first – it was ingested, but not the project semantic.
Setup 2: I have added project semantic first – it was ingested, but not the project main.
It is clear that the SA has access in both projects to collect the metadata, but somehow only the first project is ingested in any of the set-up.
Expected behavior
It works as documented
This issue seems to be present for a few releases. However connector documentation still says it is possible https://docs.open-metadata.org/latest/connectors/database/bigquery
Version:
openmetadata-ingestion[docker]==XYZ
]Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: