Zones from one project appearing as Big Query datasets in another project

[Beginner]

Hi,

I am using Dataplex under one project ("Project A") and have created "zones" against which big query datasets from another project ("Project B"), are associated.

I have now found that these "zones" which are datasets from  "Project B" are now also appearing as big query data sets (in Big Query Studio) under "Project A".

These appear as just names with no actual tables appearing when the arrow to the left is clicked on.

Is there any way to prevent these from appearing under Big Query Studio (under Project A) as they make navigating to datesets with actual tables more time consuming? Or is there a way to differentiate between those datasets with no tables (the zones, higlighted in yellow) and datasets with actual tables, higlighted in blue) without clicking on the side arrow?

[ms4446 · Accepted solution]

Unfortunately, BigQuery Studio currently lacks a built-in feature to directly hide or specifically filter out Dataplex zones that manifest as empty datasets within the view of your Project A. This situation stems from the deep integration between Google Cloud's services, designed with a focus on enhancing data discoverability and governance across different projects. 

Why This Happens:

• Seamless Integration: Dataplex and BigQuery are engineered to work in tandem, facilitating robust data management across the cloud ecosystem. Associating Dataplex zones with datasets from other projects causes BigQuery Studio to reflect these associations, aiming to simplify data access and discovery.

• Metadata Significance: These zones, while currently devoid of tables, contain crucial metadata about the datasets they're linked to. This metadata plays a key role in data governance, lineage tracking, and enables efficient querying across projects, enhancing overall data management practices.

Workarounds and Management Strategies:

• Adopt Naming Conventions: Implementing a prefix for Dataplex zones, such as "dataplex_zone_", can visually distinguish these from your regular datasets at a glance, aiding in quicker identification.

• Leverage Filtering in BigQuery Studio: Utilize the search functionality within BigQuery Studio to more effectively locate datasets. By applying the naming conventions you've established, you can either focus on datasets with tables or exclude the Dataplex zones, depending on your needs.

• Enhance Documentation and Training: Circulate guides and conduct training sessions to familiarize your team with these naming conventions and search techniques. Educating your team can significantly mitigate navigation challenges and improve efficiency in data handling.

• Submit a Feature Request: If you believe that having the ability to hide or filter out Dataplex zones directly within BigQuery Studio would significantly improve your workflow, consider submitting a feature request via Google Issue Tracker . A higher volume of requests for this functionality might prompt Google to prioritize the development of more nuanced filtering or display options for a better user experience.

[Beginner]

Thanks very much for the detailed explanation and the various options suggested. Your comments have been very helpful!