Does Atlan support nested columns beyond level 1?
Atlan gets the raw structure for nested columns beyond level 1 from JSON files, which are then parsed and rendered on the table asset sidebar. However, nested columns beyond level 1 can only be viewed and not enriched with metadata. For example, if you attach a tag to a level 1 column, the tag will not be propagated to the nested columns.
How to debug test authentication and preflight check errors?
Invalid project ID
Provided GCP project ID is invalid, please check and try again.
- Ensure that the project ID is non-empty and matches the expected project in your Google Cloud console.
Invalid service account JSON
Following are the possible error messages for this issue:
Provided Service account JSON is invalid, please check and try again.
Private key in the service account JSON is invalid, please check and try again.
Failed to sign service account access token request with the provided private key. Check the service account JSON and try again.
Malformed JSON, please check and try again.
- These indicate issues with the service account JSON key, possibly invalid or malformed data, or incorrect private key or formatting.
- Verify that the service account JSON is correctly formatted, and the private key is correctly specified.
- Regenerate the service account key if needed, and ensure that all required fields are included.
- Ensure that the file is not corrupted and follows a proper JSON structure.
Insufficient permissions
Service account doesn't have permission to create jobs, please ensure that the service account has the 'bigquery.jobs.create' permission.
- Ensure that you have assigned the
bigquery.jobs.createpermission to the service account. - Review the roles and permissions assigned to the service account in your Google Cloud IAM settings.
Cloud Resource Manager API disabled
Cloud Resource Manager API has not been used in the configured project before
or it is disabled. Please enable it and try again after some time.
- Open your Google Cloud console and enable the Cloud Resource Manager API for the project.
- Wait for the API to be fully activated before retrying the operation.
Invalid grant, service account not found
Unable to get access token for the provided service account, ensure the service account is active and try again.
- The service account is either inactive or does not exist.
- Ensure that the service account you created still exists in your Google Cloud console and has neither been disabled nor deleted.
General connection failure
Following are the possible error messages for this issue:
Unable to connect to the configured BigQuery instance, please check your credentials and configs and then try again.
Cannot create poolable connection factory.
- These indicate a general connection failure to your Google BigQuery instance, possibly due to misconfigured credentials or network issues.
- Verify that your credentials are correctly configured.
- Ensure that there are no network issues blocking the connection.
- If the problem still persists after verifying all of the above, contact Atlan support.