Reference documentation and code samples for the Google Cloud Dataplex V1 Client class BigQueryPublishingConfig.
Describes BigQuery publishing configurations.
Generated from protobuf message google.cloud.dataplex.v1.DataDiscoverySpec.BigQueryPublishingConfig
Namespace
Google \ Cloud \ Dataplex \ V1 \ DataDiscoverySpec
Methods
__construct
Constructor.
Parameters
Name
Description
data
array
Optional. Data for populating the Message object.
↳ table_type
int
Optional. Determines whether to publish discovered tables as BigLake external tables or non-BigLake external tables.
↳ connection
string
Optional. The BigQuery connection used to create BigLake tables. Must be in the form projects/{project_id}/locations/{location_id}/connections/{connection_id}
↳ location
string
Optional. The location of the BigQuery dataset to publish BigLake external or non-BigLake external tables to. 1. If the Cloud Storage bucket is located in a multi-region bucket, then BigQuery dataset can be in the same multi-region bucket or any single region that is included in the same multi-region bucket. The datascan can be created in any single region that is included in the same multi-region bucket 2. If the Cloud Storage bucket is located in a dual-region bucket, then BigQuery dataset can be located in regions that are included in the dual-region bucket, or in a multi-region that includes the dual-region. The datascan can be created in any single region that is included in the same dual-region bucket. 3. If the Cloud Storage bucket is located in a single region, then BigQuery dataset can be in the same single region or any multi-region bucket that includes the same single region. The datascan will be created in the same single region as the bucket. 4. If the BigQuery dataset is in single region, it must be in the same single region as the datascan. For supported values, refer to https://cloud.google.com/bigquery/docs/locations#supported_locations.
getTableType
Optional. Determines whether to publish discovered tables as BigLake
external tables or non-BigLake external tables.
Returns
Type
Description
int
Enum of type TableType.
setTableType
Optional. Determines whether to publish discovered tables as BigLake
external tables or non-BigLake external tables.
Parameter
Name
Description
var
int
Enum of type TableType.
Returns
Type
Description
$this
getConnection
Optional. The BigQuery connection used to create BigLake tables.
Must be in the form
projects/{project_id}/locations/{location_id}/connections/{connection_id}
Returns
Type
Description
string
setConnection
Optional. The BigQuery connection used to create BigLake tables.
Must be in the form
projects/{project_id}/locations/{location_id}/connections/{connection_id}
Parameter
Name
Description
var
string
Returns
Type
Description
$this
getLocation
Optional. The location of the BigQuery dataset to publish BigLake
external or non-BigLake external tables to.
If the Cloud Storage bucket is located in a multi-region bucket, then
BigQuery dataset can be in the same multi-region bucket or any single
region that is included in the same multi-region bucket. The datascan can
be created in any single region that is included in the same multi-region
bucket
If the Cloud Storage bucket is located in a dual-region bucket, then
BigQuery dataset can be located in regions that are included in the
dual-region bucket, or in a multi-region that includes the dual-region.
The datascan can be created in any single region that is included in the
same dual-region bucket.
If the Cloud Storage bucket is located in a single region, then
BigQuery dataset can be in the same single region or any multi-region
bucket that includes the same single region. The datascan will be created
in the same single region as the bucket.
Optional. The location of the BigQuery dataset to publish BigLake
external or non-BigLake external tables to.
If the Cloud Storage bucket is located in a multi-region bucket, then
BigQuery dataset can be in the same multi-region bucket or any single
region that is included in the same multi-region bucket. The datascan can
be created in any single region that is included in the same multi-region
bucket
If the Cloud Storage bucket is located in a dual-region bucket, then
BigQuery dataset can be located in regions that are included in the
dual-region bucket, or in a multi-region that includes the dual-region.
The datascan can be created in any single region that is included in the
same dual-region bucket.
If the Cloud Storage bucket is located in a single region, then
BigQuery dataset can be in the same single region or any multi-region
bucket that includes the same single region. The datascan will be created
in the same single region as the bucket.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-09 UTC."],[],[],null,["# Google Cloud Dataplex V1 Client - Class BigQueryPublishingConfig (1.7.1)\n\nVersion latestkeyboard_arrow_down\n\n- [1.7.1 (latest)](/php/docs/reference/cloud-dataplex/latest/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [1.7.0](/php/docs/reference/cloud-dataplex/1.7.0/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [1.6.1](/php/docs/reference/cloud-dataplex/1.6.1/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [1.4.0](/php/docs/reference/cloud-dataplex/1.4.0/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [1.3.0](/php/docs/reference/cloud-dataplex/1.3.0/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [1.2.1](/php/docs/reference/cloud-dataplex/1.2.1/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [1.1.1](/php/docs/reference/cloud-dataplex/1.1.1/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [1.0.1](/php/docs/reference/cloud-dataplex/1.0.1/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.16.1](/php/docs/reference/cloud-dataplex/0.16.1/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.15.1](/php/docs/reference/cloud-dataplex/0.15.1/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.14.0](/php/docs/reference/cloud-dataplex/0.14.0/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.13.0](/php/docs/reference/cloud-dataplex/0.13.0/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.12.0](/php/docs/reference/cloud-dataplex/0.12.0/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.11.1](/php/docs/reference/cloud-dataplex/0.11.1/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.10.0](/php/docs/reference/cloud-dataplex/0.10.0/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.9.0](/php/docs/reference/cloud-dataplex/0.9.0/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.8.0](/php/docs/reference/cloud-dataplex/0.8.0/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.7.0](/php/docs/reference/cloud-dataplex/0.7.0/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.6.0](/php/docs/reference/cloud-dataplex/0.6.0/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.5.1](/php/docs/reference/cloud-dataplex/0.5.1/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.4.0](/php/docs/reference/cloud-dataplex/0.4.0/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.3.0](/php/docs/reference/cloud-dataplex/0.3.0/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.2.3](/php/docs/reference/cloud-dataplex/0.2.3/V1.DataDiscoverySpec.BigQueryPublishingConfig)\n- [0.1.6](/php/docs/reference/cloud-dataplex/0.1.6/V1.DataDiscoverySpec.BigQueryPublishingConfig) \nReference documentation and code samples for the Google Cloud Dataplex V1 Client class BigQueryPublishingConfig.\n\nDescribes BigQuery publishing configurations.\n\nGenerated from protobuf message `google.cloud.dataplex.v1.DataDiscoverySpec.BigQueryPublishingConfig`\n\nNamespace\n---------\n\nGoogle \\\\ Cloud \\\\ Dataplex \\\\ V1 \\\\ DataDiscoverySpec\n\nMethods\n-------\n\n### __construct\n\nConstructor.\n\n### getTableType\n\nOptional. Determines whether to publish discovered tables as BigLake\nexternal tables or non-BigLake external tables.\n\n### setTableType\n\nOptional. Determines whether to publish discovered tables as BigLake\nexternal tables or non-BigLake external tables.\n\n### getConnection\n\nOptional. The BigQuery connection used to create BigLake tables.\n\nMust be in the form\n`projects/{project_id}/locations/{location_id}/connections/{connection_id}`\n\n### setConnection\n\nOptional. The BigQuery connection used to create BigLake tables.\n\nMust be in the form\n`projects/{project_id}/locations/{location_id}/connections/{connection_id}`\n\n### getLocation\n\nOptional. The location of the BigQuery dataset to publish BigLake\nexternal or non-BigLake external tables to.\n\n1. If the Cloud Storage bucket is located in a multi-region bucket, then BigQuery dataset can be in the same multi-region bucket or any single region that is included in the same multi-region bucket. The datascan can be created in any single region that is included in the same multi-region bucket\n2. If the Cloud Storage bucket is located in a dual-region bucket, then BigQuery dataset can be located in regions that are included in the dual-region bucket, or in a multi-region that includes the dual-region. The datascan can be created in any single region that is included in the same dual-region bucket.\n3. If the Cloud Storage bucket is located in a single region, then BigQuery dataset can be in the same single region or any multi-region bucket that includes the same single region. The datascan will be created in the same single region as the bucket.\n4. If the BigQuery dataset is in single region, it must be in the same single region as the datascan. For supported values, refer to \u003chttps://cloud.google.com/bigquery/docs/locations#supported_locations\u003e.\n\n### setLocation\n\nOptional. The location of the BigQuery dataset to publish BigLake\nexternal or non-BigLake external tables to.\n\n1. If the Cloud Storage bucket is located in a multi-region bucket, then BigQuery dataset can be in the same multi-region bucket or any single region that is included in the same multi-region bucket. The datascan can be created in any single region that is included in the same multi-region bucket\n2. If the Cloud Storage bucket is located in a dual-region bucket, then BigQuery dataset can be located in regions that are included in the dual-region bucket, or in a multi-region that includes the dual-region. The datascan can be created in any single region that is included in the same dual-region bucket.\n3. If the Cloud Storage bucket is located in a single region, then BigQuery dataset can be in the same single region or any multi-region bucket that includes the same single region. The datascan will be created in the same single region as the bucket.\n4. If the BigQuery dataset is in single region, it must be in the same single region as the datascan. For supported values, refer to \u003chttps://cloud.google.com/bigquery/docs/locations#supported_locations\u003e."]]