Package-level declarations
Types
/*
Describe CSV and similar semi-structured data formats.
Describe JSON data format.
Settings to manage the metadata discovery and publishing for an asset.
Status of discovery for an asset.
The aggregated data statistics for the asset reported by discovery.
Identifies the cloud resource that is referenced by this asset.
Status of the resource referenced by an asset.
Security policy status of the asset. Data security policy, i.e., readers, writers & owners, should be specified in the lake/zone/asset IAM policy.
Aggregated status of the underlying assets of a lake or zone.
Configuration for Notebook content.
Configuration for the Sql Script content.
DataAccessSpec holds the access control configuration to be enforced on data stored within resources (eg: rows, columns in BigQuery Tables). When associated with data, the data is only accessible to principals explicitly granted access through the DataAccessSpec. Principals with access to the containing resource are not implicitly granted access.
Represents a subresource of the given resource, and associated bindings with it. Currently supported subresources are column and partition schema fields within a table.
The profile information for each field type.
The profile information for a string type field.
Top N non-null values in the scanned data.
A field within a table.
Contains name, type, mode and field type specific profile information.
DataProfileResult defines the output of DataProfileScan. Each field of the table will have field type specific profile result.
DataProfileScan related setting.
DataQualityDimensionResult provides a more detailed, per-dimension view of the results.
The output of a DataQualityScan.
Evaluates whether each column value is null.
Evaluates whether each column value lies between a specified range.
Evaluates whether each column value matches a specified regex.
A rule captures data quality intent about a data source.
DataQualityRuleResult provides a more detailed, per-rule view of the results.
Evaluates whether each row passes the specified condition.The SQL expression needs to use BigQuery standard SQL syntax and should produce a boolean value per row as the result.Example: col1 >= 0 AND col2 < 10
Evaluates whether each column value is contained by a specified set.
Evaluates whether the provided expression is true.The SQL expression needs to use BigQuery standard SQL syntax and should produce a scalar boolean result.Example: MIN(col1) >= 0
Evaluates whether the column has duplicates.
DataQualityScan related setting.
DataScan execution settings.
Status of the data scan execution.
The data source for DataScan.
Provides compatibility information for a specific metadata store.
Provides compatibility information for various metadata stores.
URI Endpoints to access sessions associated with the Environment.
Compute resources associated with the analyze interactive workloads.
Configuration for the underlying infrastructure used to run workloads.
Configuration for sessions created for this environment.
Status of sessions created for this environment.
Settings to manage association of Dataproc Metastore with a lake.
Status of Lake and Dataproc Metastore service instance association.
A data range denoted by a pair of start/end values of a field.
The data scanned during processing (e.g. in incremental DataScan)
Represents a key field within the entity's partition structure. You could have up to 20 partition fields, but only the first 10 partitions have the filtering ability due to performance consideration. Note: Partition fields are immutable.
Schema information describing the structure and layout of the data.
Represents a column field within a table schema.
Describes the access mechanism of the data within its storage location.
Describes CSV and similar semi-structured data formats.
Describes Iceberg data format.
Describes JSON data format.
Describes the format of the data within its storage location.
Status of the task execution (e.g. Jobs).
Batch compute resources associated with the task.
Configuration for the underlying infrastructure used to run workloads.
Cloud VPC Network used to run the infrastructure.
Config for running scheduled notebooks.
User-specified config for running a Spark task.
The scan runs once via RunDataScan API.
DataScan scheduling and trigger settings.
The scan is scheduled to run periodically.
Describe CSV and similar semi-structured data formats.
Describe JSON data format.
Settings to manage the metadata discovery and publishing in a zone.
Settings for resources attached as assets within a zone.
Specifies the audit configuration for a service. The configuration determines which permission types are logged, and what identities, if any, are exempted from logging. An AuditConfig must have one or more AuditLogConfigs.If there are AuditConfigs for both allServices and a specific service, the union of the two AuditConfigs is used for that service: the log_types specified in each AuditConfig are enabled, and the exempted_members in each AuditLogConfig are exempted.Example Policy with multiple AuditConfigs: { "audit_configs": [ { "service": "allServices", "audit_log_configs": [ { "log_type": "DATA_READ", "exempted_members": "user:jose@example.com" }, { "log_type": "DATA_WRITE" }, { "log_type": "ADMIN_READ" } ] }, { "service": "sampleservice.googleapis.com", "audit_log_configs": [ { "log_type": "DATA_READ" }, { "log_type": "DATA_WRITE", "exempted_members": "user:aliya@example.com" } ] } ] } For sampleservice, this policy enables DATA_READ, DATA_WRITE and ADMIN_READ logging. It also exempts jose@example.com from DATA_READ logging, and aliya@example.com from DATA_WRITE logging.
Provides the configuration for logging a type of permissions. Example: { "audit_log_configs": [ { "log_type": "DATA_READ", "exempted_members": "user:jose@example.com" }, { "log_type": "DATA_WRITE" } ] } This enables 'DATA_READ' and 'DATA_WRITE' logging, while exempting jose@example.com from DATA_READ logging.
Associates members, or principals, with a role.
Represents a textual expression in the Common Expression Language (CEL) syntax. CEL is a C-like expression language. The syntax and semantics of CEL are documented at https://github.com/google/cel-spec.Example (Comparison): title: "Summary size limit" description: "Determines if a summary is less than 100 chars" expression: "document.summary.size() < 100" Example (Equality): title: "Requestor is owner" description: "Determines if requestor is the document owner" expression: "document.owner == request.auth.claims.email" Example (Logic): title: "Public documents" description: "Determine whether the document should be publicly visible" expression: "document.type != 'private' && document.type != 'internal'" Example (Data Manipulation): title: "Notification string" description: "Create a notification string with a timestamp." expression: "'New message received at ' + string(document.create_time)" The exact variables and functions that may be referenced within an expression are determined by the service that evaluates it. See the service documentation for additional information.