Database Reference
In-Depth Information
We define a shell environment variable for the project ID in order to save
typing and make it easy to substitute a different project:
$ PROJECT_ID=bigquery-e2e
After you've set this environment variable, all the commands in this chapter
should work as-is using your project instead of ours.
Additionally, some of the examples require setting up state using concepts
we haven't introduced yet. For these commands, we'll use the
bq
command-line client for the sake of expediency. For example, let's start out
by creating a scratch dataset that we'll use for storing tables in this chapter.
$ bq --project_id=${PROJECT_ID} mk -d scratch
Authenticating API Access
The first thing that a Google API front-end server does, after it validates that
you sent it a well-formed request, is authenticate the user to figure out who
is making the request. On a good day, this is a simple process. On a bad day,
authentication can be the most frustrating part of trying to get two systems
to talk to each other. Sometimes you have all the data you need to call an
API, but trying to convince the other API you're who you say you are can be
far more complex than you expect.
