knitr::opts_chunk$set(
  collapse = TRUE,
  comment = "#>",
  fig.path = "man/figures/README-",
  out.width = "100%"
)

if (bigrquery:::has_internal_auth()) {
  bigrquery:::bq_auth_internal()
} else {
  knitr::opts_chunk$set(eval = FALSE)
}

bigrquery

CRAN Status R-CMD-check Codecov test coverage

The bigrquery package makes it easy to work with data stored in Google BigQuery by allowing you to query BigQuery tables and retrieve metadata about your projects, datasets, tables, and jobs. The bigrquery package provides three levels of abstraction on top of BigQuery:

Installation

The current bigrquery release can be installed from CRAN:

install.packages("bigrquery")

The newest development release can be installed from GitHub:

#install.packages("pak")
pak::pak("r-dbi/bigrquery")

Usage

Low-level API

library(bigrquery)
billing <- bq_test_project() # replace this with your project ID 
sql <- "SELECT year, month, day, weight_pounds FROM `publicdata.samples.natality`"

tb <- bq_project_query(billing, sql)
bq_table_download(tb, n_max = 10)

DBI

library(DBI)

con <- dbConnect(
  bigrquery::bigquery(),
  project = "publicdata",
  dataset = "samples",
  billing = billing
)
con 

dbListTables(con)

dbGetQuery(con, sql, n = 10)

dplyr

library(dplyr)

natality <- tbl(con, "natality")

natality %>%
  select(year, month, day, weight_pounds) %>% 
  head(10) %>%
  collect()

Important details

BigQuery account

To use bigrquery, you'll need a BigQuery project. Fortunately, if you just want to play around with the BigQuery API, it's easy to start with Google's free public data and the BigQuery sandbox. This gives you some fun data to play with along with enough free compute (1 TB of queries & 10 GB of storage per month) to learn the ropes.

To get started, open https://console.cloud.google.com/bigquery and create a project. Make a note of the "Project ID" as you'll use this as the billing project whenever you work with free sample data; and as the project when you work with your own data.

Authentication and authorization

When using bigrquery interactively, you'll be prompted to authorize bigrquery in the browser. You'll be asked if you want to cache tokens for reuse in future sessions. For non-interactive usage, it is preferred to use a service account token, if possible. More places to learn about auth:

Note that bigrquery requests permission to modify your data; but it will never do so unless you explicitly request it (e.g. by calling bq_table_delete() or bq_table_upload()). Our Privacy policy provides more info.

Useful links

Policies

Please note that the 'bigrquery' project is released with a Contributor Code of Conduct. By contributing to this project, you agree to abide by its terms.

Privacy policy



rstats-db/bigrquery documentation built on March 15, 2024, 5:32 a.m.