Preflight checks for Google BigQuery

Before running the Google BigQuery crawler, you can run preflight checks to perform the necessary technical validations. 

πŸ’ͺ Did you know? All Google BigQuery resources expose the testIamPermissions() method, which is used for permission testing in Atlan through REST API.

The following preflight checks will be completed:

Authorization

Each request requires an OAuth 2.0 access token generated via the service account key.

Assets

Metadata crawling permission

βœ… Check successful

❌ Check failed. Not all permission granted. Missing permissions:

Query and review permission

βœ… Check successful

❌ Check failed. Not all permission granted. Missing permissions:

Miner

πŸ’ͺ Did you know? Once you have crawled assets from Google BigQuery, you can mine query history.

Miner policy

Query history

βœ… Check successful

❌ Check failed. Not all permission granted. Missing permissions:

S3

βœ… Check successful if the bucket, region, and prefix combination is valid and the S3 credential passed is accessible.

❌ Check failed with error code <AWS error code> - <AWS SDK ERR message>

For example: Miner S3 credentials: failed with error code: NoSuchBucket

Crawler workflow

This checks if the selected connection exists in Atlan.

βœ… Check successful

❌ Check failed. Connection does not exist. / Check failed. Workflow artifacts are missing. Please run the crawler workflow again.

Related articles

Was this article helpful?
0 out of 0 found this helpful