DOCSLIB.ORG

Using the Bq Command-Line Tool | Bigquery | Google Cloud

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Using the Bq Command-Line Tool | Bigquery | Google Cloud 8/23/2020 Using the bq command-line tool | BigQuery | Google Cloud Using the bq command-line tool The bq command-line tool is a Python-based command-line tool for BigQuery. This page contains general information on using the bq command-line tool. For a complete reference of all bq commands and ags, see bq command-line tool reference (/bigquery/docs/reference/bq-cli-reference). Before you begin Before you can use the bq command-line tool, you must use the Google Cloud Console to create or select a project and install the Cloud SDK. 1. Sign in (https://accounts.google.com/Login) to your Google Account. If you don't already have one, sign up for a new account (https://accounts.google.com/SignUp). 2. In the Cloud Console, on the project selector page, select or create a Cloud project. Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you nish these steps, you can delete the project, removing all resources associated with the project. Go to the project selector page (https://console.cloud.google.com/projectselector2/home/dashboar 3. Install and initialize the Cloud SDK (/sdk/docs). 4. BigQuery is automatically enabled in new projects. To activate BigQuery in a preexisting project, go to Enable the BigQuery API. Enable the API (https://console.cloud.google.com/ows/enableapi?apiid=bigquery) 5. BigQuery provides a sandbox (/bigquery/docs/sandbox) if you do not want to provide a credit card or enable billing for your project. The steps in this topic work for a project whether or not your project has billing enabled. If you optionally want to enable billing, see Learn how to enable billing (/billing/docs/how-to/modify-project). https://cloud.google.com/bigquery/docs/bq-command-line-tool 1/10 8/23/2020 Using the bq command-line tool | BigQuery | Google Cloud Instead of downloading and installing the Cloud SDK, you can use a pre-installed version of the Cloud SDK in Google Cloud Shell (/shell/docs). General usage Flag positioning bq supports two kinds of ags — global ags and command ags. They should be used in the order shown here: global_flag argument bq_command --command-specific_flag argument Global ags (or common ags) can be used in all commands. Command-specic ags apply to a specic command. Separate multiple global or command-specic ags using a space. For example: bal_flag argument \ bal_flag argument \ mmand \ mand-specific_flag argument \ mand-specific_flag argument You can specify command arguments in one of the following ways: --flag=argument --flag='argument' --flag="argument" --flag argument --flag 'argument' --flag "argument" https://cloud.google.com/bigquery/docs/bq-command-line-tool 2/10 8/23/2020 Using the bq command-line tool | BigQuery | Google Cloud Each of these methods is used throughout the BigQuery documentation. Some commands require the use of single or double quotes around arguments. This is often true when the argument contains spaces, commas, or other special characters. For example: ery --nouse_legacy_sql \ CT UNT(*) igquery-public-data`.samples.shakespeare' Flags with boolean values can be specied without an argument. If you specify true or false you must specify =argument. For example, this command species false for the boolean ag --use_legacy_sql by placing no at the front of the ag: ery --nouse_legacy_sql \ CT UNT(*) igquery-public-data`.samples.shakespeare' Alternatively, to specify false as the ag's argument, you would enter: ery --use_legacy_sql=false \ CT UNT(*) igquery-public-data`.samples.shakespeare' For a list of available global and command-specic ags, see bq command-line tool reference (/bigquery/docs/reference/bq-cli-reference). Geing help https://cloud.google.com/bigquery/docs/bq-command-line-tool 3/10 8/23/2020 Using the bq command-line tool | BigQuery | Google Cloud You can enter the following commands to get help for the bq command-line tool: For the installed version of bq, enter bq version. For a full list of commands, enter bq help. For a list of global ags, enter bq --help. For help on a specic command, enter bq help command. For help on a specic command plus a list of global ags, enter bq command --help. Debugging You can enter the following commands to debug bq: To see requests sent and received Add the --apilog=path_to_file ag to save a log of operations to a local le. bq works by making standard REST-based API calls, which can be useful to see. It is also useful to attach this log when reporting issues. Using - or stdout instead of a le path will print the log to the console. Setting --apilog to stderr outputs to the standard error le. To help troubleshoot errors Enter the --format=prettyjson ag when getting a job's status (/bigquery/docs/managing-jobs#view-job) or when viewing detailed information about resources such as tables and datasets. Using this ag outputs the response in JSON format, including the reason property. You can use the reason property to look up troubleshooting steps (/bigquery/troubleshooting-errors). Seing default values for command-line ags You can set default values for command-line ags by including them in the bq command-line tool's conguration le — .bigqueryrc. Before you congure your default options, you must rst create a .bigqueryrc le. You can use your preferred text editor to create the le. After you create the .bigqueryrc le, you can specify the path to the le using the --bigqueryrc global ag. https://cloud.google.com/bigquery/docs/bq-command-line-tool 4/10 8/23/2020 Using the bq command-line tool | BigQuery | Google Cloud If the --bigqueryrc ag is not specied, the BIGQUERYRC environment variable is used. If that is not specied, the path ~/.bigqueryrc is used. The default path is $HOME/.bigqueryrc. Creating a .bigqueryrc le using the bq init command is not recommended. Adding ags to .bigqueryrc To add default values for command-line ags to .bigqueryrc: Place global ags (/bigquery/docs/reference/bq-cli-reference#global_ags) at the top of the le without a header For command-specic ags (/bigquery/docs/reference/bq-cli-reference#command-specic_ags) , enter the command name (in brackets) and add the command-specic ags (one per line) below it in the following format: nd mand-specific_flag=argument mand-specific_flag=argument When you enter command-line ags in .bigqueryrc, you must specify the ag's argument in the following format =argument. .bigqueryrc is read every time you run bq so changes should be updated immediately. When you run bq in interactive mode (#interactive) (bq shell), you must restart the shell for the changes to take effect. Example This example sets default values for the following global ags: --apilog is set to stdout to print debugging output to the console. --format is set to prettyjson to display command output in a human-readable JSON format. --location is set to the US multi-region location. https://cloud.google.com/bigquery/docs/bq-command-line-tool 5/10 8/23/2020 Using the bq command-line tool | BigQuery | Google Cloud This example sets default values for the following query command-specic ags: --use_legacy_sql is set to false to make standard SQL the default query syntax. Note: You cannot use --nouse_legacy_sql in .bigqueryrc. --max_rows is set to 100 to control the number of rows in the query output. --maximum_bytes_billed is set to 10,000,000 bytes (10 MB) to fail queries that read more than 10 MB of data. This example sets a default value for the following load command-specic ag: --destination_kms_key (/bigquery/docs/customer-managed-encryption) is set to projects/myproject/locations/mylocation/keyRings/myRing/cryptoKeys/myKey. ntial_file = path_to_credential_file log=stdout mat=prettyjson ation=US y] _legacy_sql=false _rows=100 imum_bytes_billed=10000000 ] tination_kms_key=projects/myproject/locations/mylocation/keyRings/myRing/cryptoKeys/ To conrm your settings, enter the following command: ~/.bigqueryrc Running bq in an interactive shell You can run bq in an interactive shell where you don't need to prex the commands with bq. To start interactive mode, enter bq shell. After launching the shell, the prompt changes to the ID of https://cloud.google.com/bigquery/docs/bq-command-line-tool 6/10 8/23/2020 Using the bq command-line tool | BigQuery | Google Cloud your default project. To exit interactive mode, enter exit. Examples You can nd command-line examples throughout the How-to guides (/bigquery/docs/how-to) section of the BigQuery documentation. Below are links to common command-line tasks such as creating, getting, listing, deleting, and modifying BigQuery resources. Creating resources For information on using the bq command-line tool to create resources, see: Creating a dataset (/bigquery/docs/datasets#bigquery-create-dataset-cli) Creating an empty table with a schema denition (/bigquery/docs/tables#bigquery-create-table-cli) Creating a table from a query result (/bigquery/docs/tables#creating_a_table_from_a_query_result) Creating an ingestion-time partitioned table (/bigquery/docs/creating-partitioned-tables#creating_an_empty_ingestion- time_partitioned_table_with_a_schema_denition) Creating a view (/bigquery/docs/views#creating_a_view) For examples of creating a table using a data le, see Loading data (#loading_data). Geing information about resources For information on using the bq command-line tool to get information about resources, see: Getting information about datasets (/bigquery/docs/dataset-metadata#getting_dataset_information) Getting information about tables (/bigquery/docs/tables#getting_information_about_tables)
Load more

Recommended publications
  • Real-Time Backend Architecture Using Node.Js, Express and Google Cloud
    Anh Vu Real-time backend architecture using Node.js, Express and Google Cloud Platform Metropolia University of Applied Sciences Bachelor of Information Technology Information Technology Bachelor’s Thesis 5 January 2021 Abstract Anh Vu Author Real-time backend using NodeJS, Express and Google Cloud Title Platform NumBer of Pages 47 pages Date 5 January 2021 Degree Bachelor of Engineering Degree Programme Information Technology Professional Major MoBile Solutions Instructors Petri Vesikivi, Head of MoBile Solutions Real-time applications, which assure the latency within the defined time limit, are becoming more popular due to the growth of Software as a service trend. Before the evolution of cloud computing, the only solution was to use native WebSockets which are difficult to set up and develop. Recently, Google Cloud Platform provides a developer-friendly, fast and responsive platform to make the process of developing real-time applications seamless. The purpose of the thesis was to demonstrate and Build a scalaBle, high-available and reliaBle Backend architecture using Node.js and Google Cloud Platform. The thesis consists of a theoretical background including Node.js, monolithic and microservices architecture, serverless architecture and real-time dataBase, which provide basic understanding of different architectures and technical solutions. The advantages and disadvantages of the architecture were also clearly analyzed and evaluated. Furthermore, a minimum viable product for a taxi booking app was created to demonstrate the architecture usage in a real use case. To summarize, the thesis aimed to provide the insights of real-time Backend architecture using Node.js and Google Cloud Platform. Moreover, the benefits of using this technology stacks were carefully examined in a case study.
    [Show full text]
  • Create a Created Date Schema in Bigquery
    Create A Created Date Schema In Bigquery Denominative Elmore canoodles funereally. Auxiliary Rudy acquiesce: he unbar his aril adequately and contagiously. Overreaching Randolf excused some scrabble and shacks his syneresis so midnight! Wait polls with exponential backoff. The schema in tests are many cases. Perform various levels of dates in schema definition file somewhere on create date column when you created in an identical data will lead at. You'd may that avoiding two scans of SALES would improve performance However remember most circumstances the draw BY version takes about twice as suite as the lot BY version. You run some SQL queries against that data. The script then creates a partition function, if configured. The order in which clustering is done matters. Developer relations lead at SKB Kontur. We create schema in the dates and their very wide variety of bigquery operation creates a working directory as a few seconds of model you. By using the client libraries. Database services to migrate, please leave it empty. What are partitions in SQL? In our case the join condition is matching dates from the pedestrian table and the bike table. The mother source records need is have a machine image updates to merge correctly. Python community version selection works in schema of bigquery operation on create date column can be created in a new custom schema tab. Once per store the data needs to simplify etl to any data are also a bigquery? Google Analytics 360 users that have that up the automatic BigQuery export will rejoice by this. Whether to automatically infer options and schema for CSV and JSON sources.
    [Show full text]
  • Google Genomics Documentation Release V1
    Google Genomics Documentation Release v1 Google Genomics <https://cloud.google.com/genomics> Mar 07, 2018 Contents 1 Select Genomic Data to work with3 1.1 Discover Published Data.........................................3 2 Process Data on Google Cloud 19 2.1 Run workflows and common tasks in parallel.............................. 19 2.2 Run Galaxy on Compute Engine..................................... 43 2.3 Run NCBI BLAST on Compute Engine................................. 43 2.4 Run Bioconductor on Compute Engine................................. 43 2.5 Run iPython Notebooks on Compute Engine.............................. 45 3 Access Genomic Data using. 47 3.1 Integrative Genomics Viewer (IGV)................................... 47 3.2 Run Picard and GATK tools on Cloud-Resident Genomic Data..................... 49 3.3 Browse Reads with Bioconductor.................................... 54 3.4 Beacon.................................................. 55 3.5 GABrowse................................................ 55 3.6 The R client............................................... 56 3.7 Python.................................................. 56 3.8 Java.................................................... 57 3.9 Go.................................................... 57 4 Analyze Data in Google Genomics 59 4.1 Analyze Reads.............................................. 59 4.2 Analyze Variants............................................. 67 4.3 Annotate Variants............................................ 101 4.4 Perform Quality Control Checks....................................
    [Show full text]
  • Overview Objectives Exploring the Bigquery Console
    CS6502 - APPLIED BIG DATA AND VISUALIZATION (Spring 2020) Lab 3 Overview SQL (Structured Query Language) is a standard language for data operations that allows you to ask questions and get insights from structured datasets. It's commonly used in database management and allows you to perform tasks like transaction record writing into relational databases and petabyte-scale data analysis. This lab serves as an introduction to SQL and is intended to prepare you for the many labs in this course. This lab is divided into two parts: in the first half, you will learn fundamental SQL querying keywords, which you will run in the BigQuery console on a public dataset that contains information on London bikeshares. In the second half, you will learn how to export subsets of the London bikeshare dataset into CSV files, which you will then upload to Cloud SQL. From there you will learn how to use Cloud SQL to create and manage databases and tables. Towards the end, you will get hands-on practice with additional SQL keywords that manipulate and edit data. Objectives In this lab, you will learn how to: ● Distinguish databases from tables and projects. ● Use the SELECT, FROM, and WHERE keywords to construct simple queries. ● Identify the different components and hierarchies within the BigQuery console. ● Load databases and tables into BigQuery. ● Execute simple queries on tables. ● Learn about the COUNT, GROUP BY, AS, and ORDER BY keywords. ● Execute and chain the above commands to pull meaningful data from datasets. ● Export a subset of data into a CSV file and store that file into a new Cloud Storage bucket.
    [Show full text]
  • Google Cloud Shell Documentation
    8/22/2020 Google Cloud Shell documentation Google Cloud Shell documentation Google Cloud Shell is an interactive shell environment for Google Cloud Platform that makes it easy for you to learn and experiment with GCP and manage your projects and resources from your web browser. With Cloud Shell, the Cloud SDK gcloud (/sdk/gcloud) command-line tool and other utilities you need are pre- installed, fully authenticated, up-to-date, and always available when you need them. Additionally, Cloud Shell comes with a built-in code editor, the ability to launch tutorials and open cloned repositories, and preview functionality to temporarily run web apps on a Cloud Shell virtual machine instance, and more. Quicksta How-to guides Get started with Cloud Shell Learn a task (/shell/docs/quickstart) (/shell/docs/how-to) APIs and reference Concepts Cloud Shell REST and RPC API Develop a deep understanding of reference documentation Cloud Shell (/shell/docs/apis) (/shell/docs/concepts) Suppo Resources Get assistance with Cloud Shell Pricing, quotas, and release notes issues (/shell/docs/pricing) (/shell/docs/getting-support) Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License (https://creativecommons.org/licenses/by/4.0/), and code samples are licensed under the Apache 2.0 License (https://www.apache.org/licenses/LICENSE-2.0). For details, see the Google Developers Site Policies (https://developers.google.com/site-policies). Java is a registered trademark of Oracle and/or its aliates. https://cloud.google.com//shell/docs/ 1/1.
    [Show full text]
  • TR-4653: Netapp Private Storage for Google Cloud Platform
    Technical Report NetApp Private Storage for Google Cloud Platform Solution Architecture and Deployment Guide Mark Beaupre and Alim Karim, NetApp January 2018 | TR-4653 Abstract This document describes the architecture of NetApp Private Storage for Google Cloud Platform (GCP). TABLE OF CONTENTS 1 NetApp Private Storage for GCP Solution Overview ...................................................................3 1.1 Assumptions ...........................................................................................................................................................3 1.2 Use Case Overview ...............................................................................................................................................3 1.3 Technical Overview................................................................................................................................................3 2 NetApp Private Storage for GCP Solution Architecture ..............................................................4 2.1 Solution Architecture Components .......................................................................................................................4 2.2 Solution Architecture Diagram...............................................................................................................................7 2.3 Solution Architecture Security Elements...............................................................................................................8 3 NetApp Private Storage for GCP Deployment
    [Show full text]
  • (SOC) 3 Report on the Google Cloud Platform System Relevant To
    System and Organization Controls (SOC) 3 Report on the Google Cloud Platform System Relevant to Security, Availability, and Confidentiality For the Period 1 May 2018 to 30 April 2019 Google LLC 1600 Amphitheatre Parkway Mountain View, CA, 94043 650 253-0000 main Google.com Management’s Report of its Assertion on the Effectiveness of Its Controls Over the Google Cloud Platform System Based on the Trust Services Criteria for Security, Availability, and Confidentiality We, as management of, Google LLC (“Google” or “the Company”) are responsible for: · Identifying the Google Cloud Platform System (System) and describing the boundaries of the System, which are presented in Attachment A · Identifying our principal service commitments and system requirements · Identifying the risks that would threaten the achievement of its principal service commitments and system requirements that are the objectives of our system, which are presented in Attachment B · Identifying, designing, implementing, operating, and monitoring effective controls over the System to mitigate risks that threaten the achievement of the principal service commitments and system requirement · Selecting the trust services categories that are the basis of our assertion We assert that the controls over the system were effective throughout the period 1 May 2018 to 30 April 2019, to provide reasonable assurance that the principal service commitments and system requirements were achieved based on the criteria relevant to security, availability, and confidentiality set forth in the AICPA’s
    [Show full text]
  • Google PROFESSIONAL-DATA-ENGINEER Exam Google Cloud Data Engineer Professional Exam
    Questions & Answers PDF P-1 Google PROFESSIONAL-DATA-ENGINEER Exam Google Cloud Data Engineer Professional Exam Questions & Answers (Retail Version – Full Questions Set) http://www.justcerts.com Questions & Answers PDF P-2 Product Questions: 240/2Case Study Version: 11.0 Mix Questions Set A Question: 1 Your company built a TensorFlow neutral-network model with a large number of neurons and layers. The model fits well for the training data. However, when tested against new data, it performs poorly. What method can you employ to address this? A. Threading B. Serialization C. Dropout Methods D. Dimensionality Reduction Answer: C Explanation: Reference https://medium.com/mlreview/a-simple-deep-learning-model-for-stock-price-prediction- using-tensorflow-30505541d877 Question: 2 You are building a model to make clothing recommendations. You know a user’s fashion preference is likely to change over time, so you build a data pipeline to stream new data back to the model as it becomes available. How should you use this data to train the model? A. Continuously retrain the model on just the new data. B. Continuously retrain the model on a combination of existing data and the new data. C. Train on the existing data while using the new data as your test set. D. Train on the new data while using the existing data as your test set. Answer: D Question: 3 You designed a database for patient records as a pilot project to cover a few hundred patients in three clinics. Your design used a single database table to represent all patients and their visits, and you used self-joins to generate reports.
    [Show full text]
  • Intro to Google Cloud
    An Introduction to Cloud Shell (in less than 5 minutes) brought to you by The ISB Cancer Genomics Cloud Cloud Shell is a Debian Linux VM with a 5GB persistent disk that you can access directly from the Console. Just click on the Activate Google Cloud Shell button at the top of the Google Cloud Platform Console. The VM is provisioned on a per-user, per-session basis, will persist while your Cloud Shell session is active, and will terminate after an hour of inactivity. Certain tools come pre-installed and you can install additional tools or copy files to your home directory as needed. This data will persist between sessions and is private to you and available across projects. The first time you activate the Cloud Shell, you will see this introductory pop-up. Click Start Cloud Shell. The Cloud Shell session opens inside a new frame at the bottom of the console. It can take a few seconds for the session to be initialized. Once you see the prompt, your Cloud Shell session is ready to use. You can minimize, open in a new window, or close your Cloud Shell session using the controls in the upper right corner. You can also open additional shell sessions as additional tabs using the + symbol, or close existing sessions using the x. You can access settings and other information from the gear icon. Popping the shell out into its own window lets you resize it and gives you more space to work. Let’s install a few additional Python packages so that we can run the ISB-CGC python examples.
    [Show full text]
  • HPE Digital Learner Google Cloud for Architects (Intermediate) Content Pack
    Content Pack data sheet HPE Digital Learner Google Cloud for Architects (Intermediate) Content Pack This self-paced eLearning Content Pack provides the required HPE Content Pack CP019 number training to help transition from a traditional IT architect role to a cloud architect role utilizing the Google public cloud Content Pack 22 Hours length environment. This is a comprehensive intermediate training Content Pack Category 2 series that includes many core areas required to plan, design category and implement modern cloud infrastructures, applications and Learn more View now data within the Google public cloud. This training is intended for IT personnel who need to rapidly uplift their IT/cloud skills as part of an ongoing business and operational strategy to migrate IT to the Google public cloud. Why HPE Education Services? • IDC MarketScape leader 5 years running for IT education and training* Audience • Recognized by IDC for leading with global coverage, unmatched technical • IT professionals, including managers, Google public cloud domain as part of an expertise, and targeted education engineers and developers, evaluating or ongoing hybrid cloud strategy. Areas of focus consulting services* implementing application environments on include Google cloud introductory • Key partnerships with industry leaders Google Cloud Platform fundamentals training as well as specific OpenStack®, VMware®, Linux®, Microsoft®, and detailed technology training around a ITIL, PMI, CSA, and SUSE • Data professionals responsible for provisioning and optimizing
    [Show full text]
  • Google Cloud. | 1
    google cloud. | 1 how the google cloud works. *this is a study guide that was created from lecture videos and is used to help you gain an understanding of how the google cloud works. Google Cloud Services Foundations GCP- google cloud platform compute for virtualization, storage and other services Compute Services- virtual machines, containers and container management (Docker) and functions and lambdas.serverless computing Storage Services- files, archival storage, persistent disks for virtual machines Data Services- NoSQL, RDBMS, Hadoop and Spark Big Data Services- data pipelines, data warehouses, data science notebooks, machine learning Other services- security and identity, management and monitoring from Stackdriver, developer tools Why Use Google Cloud?- Cloud services allow you to get to market faster. Scalable services save time for developers and DevOps. Automatic usage discounts equal less management of pricing. mind movement machine. google cloud. | 2 Automatic scaling- build app and has as many customers as possible without running out of resources. The default is autoscale until you put a limit. GCP is fast, has frequent improvements, autoscales massively and a good value. GCP has an engineering focus and has documentation challenges and pricing surprises. Gcutil is a tool that is a part of the SDK and is used from the command line. Use gmail account -> use free trial -> have credit card available Working with the console- Google Cloud Console is a browser or web page that gives you the ability to work with cloud services that are available on GCP. Google works best in Chrome. Setting the location, where physically are the virtual machines, databases and etc.
    [Show full text]
  • Building a Document Understanding Pipeline with Google Cloud | Google Cloud Blog
    8/23/2020 Building a Document Understanding Pipeline with Google Cloud | Google Cloud Blog Blog Menu AI & M ACH INE LEARNING Building a document understanding pipeline with Google Cloud Holt Skinner Cloud Technical Resident Find an article... Michael Munn Machine Learning Solutions Engineer Latest storiMesichael Sherman Machine Learning Engineer Products September 20, 2019 Topics About Document understanding is the practice of using AI and machine learning to extract RSS Feed data and insights from text and paper sources such as emails, PDFs, scanned documents, and more. In the past, capturing this unstructured or “dark data” has been an expensive, time-consuming, and error-prone process requiring manual data entry. https://cloud.google.com/blog/products/ai-machine-learning/building-a-document-understanding-pipeline-with-google-cloud 1/10 8/23/2020 p Building a Dgocument Undersptanding Ppipeline with Goqogle Clogud | Google Cloud Blog y Today, AI and machine learning have made great advances towards automating this process, enabling businesses to derive insights from and take advantage of this data that had been previously untapped. Blog Menu In a nutshell, document understanding allows you to: Organize documents Extract knowledge from documents Increase processing speed At Google Cloud we provide a solution, Document AI, which enterprises can leverage in collaboration with partners to implement document understanding. However, many developers have both the desire and the technical expertise to build their own document understanding pipelines on Google Cloud Platform (GCP)—without working with a partner—using the individual Document AI products. If that sounds like you, this post will take you step-by-step through a complete document understanding pipeline.
    [Show full text]