Analyze Google Translate Data in R via JDBC

Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
Use standard R functions and the development environment of your choice to analyze Google Translate data with the CData JDBC Driver for Google Translate.

Access Google Translate data with pure R script and standard SQL on any machine where R and Java can be installed. You can use the CData JDBC Driver for Google Translate and the RJDBC package to work with remote Google Translate data in R. By using the CData Driver, you are leveraging a driver written for industry-proven standards to access your data in the popular, open-source R language. This article shows how to use the driver to execute SQL queries to Google Translate and visualize Google Translate data by calling standard R functions.

Install R

You can match the driver's performance gains from multi-threading and managed code by running the multithreaded Microsoft R Open or by running open R linked with the BLAS/LAPACK libraries. This article uses Microsoft R Open 3.2.3, which is preconfigured to install packages from the Jan. 1, 2016 snapshot of the CRAN repository. This snapshot ensures reproducibility.

Load the RJDBC Package

To use the driver, download the RJDBC package. After installing the RJDBC package, the following line loads the package:

library(RJDBC)

Connect to Google Translate as a JDBC Data Source

You will need the following information to connect to Google Translate as a JDBC data source:

  • Driver Class: Set this to cdata.jdbc.api.APIDriver
  • Classpath: Set this to the location of the driver JAR. By default this is the lib subfolder of the installation folder.

The DBI functions, such as dbConnect and dbSendQuery, provide a unified interface for writing data access code in R. Use the following line to initialize a DBI driver that can make JDBC requests to the CData JDBC Driver for Google Translate:

driver <- JDBC(driverClass = "cdata.jdbc.api.APIDriver", classPath = "MyInstallationDir\lib\cdata.jdbc.api.jar", identifier.quote = "'") 

You can now use DBI functions to connect to Google Translate and execute SQL queries. Initialize the JDBC connection with the dbConnect function.

Authentication

Google Cloud Translation API requires OAuth 2.0 authentication to ensure secure access to translation services, datasets, glossaries, and adaptive MT resources. This authentication method allows you to securely connect to your Google Cloud project and manage translation resources with proper authorization.

OAuth 2.0 Setup and Configuration

Step 1: Create Google Cloud Project and Enable API

To set up OAuth authentication:

  1. Visit the Google Cloud Console
  2. Create a new project or select an existing project
  3. Note down your Project ID (required for all API calls)
  4. Navigate to "APIs & Services" > "Library"
  5. Search for and enable the "Cloud Translation API"
  6. Go to "APIs & Services" > "Credentials"
  7. Click "Create Credentials" and select "OAuth Client ID"
  8. Configure the OAuth consent screen if prompted
  9. Select "Desktop application" or "Web application" as appropriate
  10. Set the authorized redirect URI (CallbackURL)
  11. Copy the Client ID and Client Secret for use in your connection

Required Connection Properties

  • AuthScheme: Set this to OAuth (required)
  • OAuthClientId: Client ID from Google Cloud Console (required)
  • OAuthClientSecret: Client secret from Google Cloud Console (required)
  • CallbackURL: Redirect URI specified in your OAuth application (required)
  • InitiateOAuth: Set to GETANDREFRESH for automatic token management (recommended)
  • ProjectId: Your Google Cloud project ID or project number (required for queries)

Required OAuth Scopes

The Google Cloud Translation API Profile requires the following OAuth scope:

  • https://www.googleapis.com/auth/cloud-translation - Full access to Cloud Translation API resources including translation, datasets, glossaries, and adaptive MT

Built-in Connection String Designer

For assistance in constructing the JDBC URL, use the connection string designer built into the Google Translate JDBC Driver. Either double-click the JAR file or execute the jar file from the command-line.

java -jar cdata.jdbc.api.jar

Fill in the connection properties and copy the connection string to the clipboard.

Below is a sample dbConnect call, including a typical JDBC connection string:

conn <- dbConnect(driver,"jdbc:api:Profile=C:\profiles\GoogleTranslate.apip;AuthScheme=OAuth;InitiateOAuth=GETANDREFRESH;OAuthClientId=your_client_id;OAuthClientSecret=your_client_secret;CallbackUrl=your_callback_url;")

Schema Discovery

The driver models Google Translate APIs as relational tables, views, and stored procedures. Use the following line to retrieve the list of tables:

dbListTables(conn)

Execute SQL Queries

You can use the dbGetQuery function to execute any SQL query supported by the Google Translate API:

supportedlanguages <- dbGetQuery(conn,"SELECT LanguageCode, DisplayName FROM SupportedLanguages WHERE ProjectId = 'my-project-12345'")

You can view the results in a data viewer window with the following command:

View(supportedlanguages)

Plot Google Translate Data

You can now analyze Google Translate data with any of the data visualization packages available in the CRAN repository. You can create simple bar plots with the built-in bar plot function:

par(las=2,ps=10,mar=c(5,15,4,2))
barplot(supportedlanguages$DisplayName, main="Google Translate SupportedLanguages", names.arg = supportedlanguages$LanguageCode, horiz=TRUE)

Ready to get started?

Connect to live data from Google Translate with the API Driver

Connect to Google Translate