bq command-line tool

Related topics

• BigQuery works with bq command-line tool From the official documentation: “You can use the [Google Cloud console](/bigquery/docs/bigquery-web-ui) or the `bq command-line tool` for interactive querying.”
• BigQuery Studio is an alternative to bq command-line tool From the official documentation: “The following are supported only when you query a linked BigQuery dataset by using the **BigQuery Studio** and **Looker Studio** pages, or by using the [bq command-line tool](/bigquery/docs/reference/bq-cli-reference):”
• bq command-line tool is part of BigQuery From the official documentation: “BigQuery interfaces include Google Cloud console interface and the BigQuery command-line tool.”
• bq command-line tool configures BigQuery Data Transfer Service From the official documentation: “To configure and manage transfers, you can use the [Google Cloud console](/bigquery/docs/bigquery-web-ui), the [bq command-line tool](/bigquery/docs/reference/bq-cli-reference), or the [BigQuery Data Transfer Service API](/bigquery/docs/reference/datatransfer/rest).”
• bq command-line tool works with Cloud Storage From the official documentation: “Use the `bq load` command, specify `NEWLINE_DELIMITED_JSON` using the `--source_format` flag, and include a [Cloud Storage URI](/bigquery/docs/batch-loading-data#gcs-uri).”
• bq command-line tool is an alternative to Google Cloud CLI From the official documentation: “You can also submit a batch translation job by using a translation configuration file with the Google Cloud CLI (`gcloud bq migration-workflows`) or with the bq command-line tool command-line tool.”
• bq command-line tool configures transfer configuration From the official documentation: “Scheduled queries are a kind of transfer. To update scheduled query, you can use the bq command-line tool to make a transfer configuration.”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Storage From the official documentation: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
• BigQuery works with Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• Customer-Managed Encryption Keys secures Cloud Storage From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• BigQuery works with BigQuery Data Transfer Service From the official documentation: “The BigQuery Data Transfer Service uses load jobs to load Amazon S3 data into BigQuery.”
• Cloud Storage works with Google Cloud CLI From the official documentation: “The gcloud CLI is the preferred command line tool for accessing Cloud Storage.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• Cloud Logging works with Pub/Sub From the official documentation: “Pub/Sub writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Storage works with Customer-Managed Encryption Keys From the official documentation: “Cloud Storage supports CMEK for routing logs.”
• Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Cloud Logging works with Cloud Storage From the official documentation: “Cloud Storage writes various log entries to Cloud Logging in the Google Cloud console.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• Customer-Managed Encryption Keys secures BigQuery From the official documentation: “You can either create CMEKs manually to protect your BigQuery resources or use Cloud KMS Autokey.”
• Customer-Managed Encryption Keys secures Pub/Sub From the official documentation: “Encrypt Pub/Sub topic with CMEK”
• BigQuery works with Managed Service for Apache Airflow From the official documentation: “You can use Managed Airflow to orchestrate services in your data pipelines, such as triggering a job in BigQuery or starting a Dataflow pipeline.”
• BigQuery is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• BigQuery Data Transfer Service works with Cloud Storage From the official documentation: “- [Cloud Storage](/bigquery/docs/cloud-storage-transfer)”
• Cloud Storage bucket is part of Cloud Storage From the official documentation: “Create a Google Cloud Storage bucket”
• Customer-Managed Encryption Keys secures Managed Service for Apache Airflow From the official documentation: “This page describes how to use [Customer Managed Encryption Keys (CMEK)](/kms/docs/cmek) to protect Managed Airflow environments.”
• BigQuery depends on Cloud Logging From the official documentation: “BigQuery utilizes Cloud Logging for some of your log data.”
• BigQuery works with transfer configuration From the official documentation: “Disabling a transfer does **not** remove any data already transferred to BigQuery.”
• BigQuery Data Transfer Service works with Cloud Logging From the official documentation: “The BigQuery Data Transfer Service exports logs and metrics to Cloud Monitoring and Cloud Logging that provide observability into your transfers.”
• BigQuery Data Transfer Service works with Pub/Sub From the official documentation: “If you intend to set up transfer run notifications for Pub/Sub, you must have `pubsub.topics.setIamPolicy` permissions.”
• BigQuery Data Transfer Service works with scheduled query From the official documentation: “- [Scheduled Queries](/bigquery/docs/scheduling-queries#using_a_service_account)”
• Cloud Logging is an alternative to Cloud Storage From the official documentation: “Instead, they are routed to either Cloud Storage (recommended) or Cloud Logging, depending on your organization's configuration.”
• Cloud Logging works with Customer-Managed Encryption Keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Cloud Storage works with Managed Service for Apache Airflow From the official documentation: “When you upload your DAG file to the `dags/` folder in Cloud Storage, Managed Airflow parses the file.”
• Customer-Managed Encryption Keys depends on Cloud Storage From the official documentation: “If used for storing Customer-managed Encryption Keys (CMEK): Cloud Storage (See [Cloud Storage pricing](/storage/pricing).)”
• scheduled query is part of BigQuery From the official documentation: “In the [Google Cloud Console](https://console.cloud.google.com/), go to **BigQuery**. 2. In the left navigation, click **Scheduled queries**.”
• transfer configuration is part of BigQuery Data Transfer Service From the official documentation: “Deletes a data transfer configuration in the BigQuery Data Transfer Service.”
• BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
• BigQuery works with Cloud Storage bucket From the official documentation: “BigQuery lets you load [Datastore](/datastore) entities from a Cloud Storage bucket into a BigQuery table for analysis.”
• BigQuery Data Transfer Service depends on Cloud Storage bucket From the official documentation: “This bucket is used by the BigQuery Data Transfer Service as a staging area for data files to be ingested into BigQuery.”
• BigQuery Data Transfer Service works with Customer-Managed Encryption Keys From the official documentation: “When you specify a CMEK with a transfer, the BigQuery Data Transfer Service applies the CMEK to any intermediate on-disk cache of ingested data so that the entire data transfer workflow is CMEK compliant.”
• BigQuery Data Transfer Service works with Managed Service for Apache Airflow From the official documentation: “**Managed Service for Apache Airflow jobs**: you can schedule [Managed Service for Apache Airflow](/composer) jobs to issue ETL jobs that create regional subsets before triggering the BigQuery Data Transfer Service through its [client API](/bigquery/docs/reference/libraries).”
• BigQuery Data Transfer Service depends on Pub/Sub From the official documentation: “The communication channel between the agent running on premises and BigQuery Data Transfer Service is by publishing Pub/Sub messages to a per transfer topic.”
• BigQuery Studio is part of BigQuery From the official documentation: “BigQuery Studio helps you discover, analyze, and run inference on data in BigQuery with the following features:”
• Cloud Logging depends on Customer-Managed Encryption Keys From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Cloud Logging is an alternative to Google Cloud CLI From the official documentation: “This section shows you how to verify the encryption key that was used during cluster creation. You can perform this verification using Cloud Logging or by using the Google Cloud CLI.”
• Cloud Logging works with Managed Service for Apache Airflow From the official documentation: “To learn about Cloud Logging and Cloud Monitoring for your Managed Airflow environment, see [Monitor environments](/composer/docs/composer-2/monitor-environments).”
• Cloud Storage works with scheduled query From the official documentation: “To automatically export Gmail logs from BigQuery to Cloud Storage on a recurring schedule, create a scheduled query using the EXPORT DATA statement.”
• Cloud Storage bucket works with Google Cloud CLI From the official documentation: “Use the following command to upload your audio file to an existing Cloud Storage bucket using the [Google Cloud CLI](/cli).”
• Customer-Managed Encryption Keys is part of BigQuery From the official documentation: “If you require more control over encryption keys, BigQuery supports [customer-managed encryption keys](/bigquery/docs/customer-managed-encryption) in the [Cloud Key Management Service](/kms/docs).”
• Customer-Managed Encryption Keys configures Cloud Logging From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Customer-Managed Encryption Keys secures Cloud Logging From the official documentation: “To use Cloud Logging with Customer-managed encryption keys (CMEK), you must complete the steps in the [Enable CMEK for an organization](/logging/docs/routing/managed-encryption#enable) page in the Cloud Logging documentation.”
• Customer-Managed Encryption Keys is part of Cloud Storage From the official documentation: “[Cloud Storage](/storage/docs/introduction) provides features such as customer-managed encryption, lifecycle management, and aging and retention policies.”
• Customer-Managed Encryption Keys configures Cloud Storage bucket From the official documentation: “If you want your data to remain encrypted with a customer-managed key during an export or import, you must set a customer-managed encryption key on the Cloud Storage bucket before exporting data to it.”
• Customer-Managed Encryption Keys secures scheduled query From the official documentation: “Optional: CMEK If you use [customer-managed encryption keys](/bigquery/docs/customer-managed-encryption), you can select **Customer-managed key** under **Advanced options**.”
• Customer-Managed Encryption Keys configures transfer configuration From the official documentation: “You can update a CMEK for a transfer if the transfer configuration was originally created with a CMEK encryption.”
• Google Cloud CLI configures Cloud Logging From the official documentation: “You can update your cluster's [Cloud Logging](/kubernetes-engine/multi-cloud/docs/aws/how-to/cloud-logging) configuration settings with the Google Cloud CLI.”
• Google Cloud CLI works with Managed Service for Apache Airflow From the official documentation: “Using the Google Cloud CLI with Managed Service for Apache Airflow”
• Managed Service for Apache Airflow depends on BigQuery From the official documentation: “This happens because Google Kubernetes Engine depends on BigQuery and Managed Service for Apache Airflow inherits this dependency from the Kubernetes Engine API.”
• Pub/Sub works with transfer configuration From the official documentation: “Create a transfer configuration, where notifications are sent to Cloud Pub/Sub when a transfer run succeeds or fails.”