[Feature] Consistent BigQuery Table Naming Convention in DBT Compilation

[karkinissan]

Is this your first time submitting a feature request?

• [X] I have read the expectations for open source contributors
• [X] I have searched the existing issues, and I could not find an existing issue for this feature
• [X] I am requesting a straightforward extension of existing dbt-bigquery functionality, rather than a Big Idea better suited to a discussion

Describe the feature

When compiling DBT models for BigQuery, the current behavior results in table names formatted as `project_id`.`dataset_name`.`table_name`. However, to align with BigQuery's standard naming conventions and improve consistency, there's a need to modify the DBT compilation process to generate table names in the format `project_id.dataset_name.table_name`.

The former format prevents a CTRL+Click on the table name in the BigQuery editor to navigate to the source table/view. Not an issue with the latter format.

Please consider implementing this feature to enhance the overall usability and consistency of DBT when working with BigQuery.

Describe alternatives you've considered

Dataform follows the BigQuery's standard naming convention.

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response

[github-actions[bot]]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

[karkinissan]

Comment to prevent closing.