Cloud

Enter the Googleverse with Exasol’s Cloud Deployment Wizard and Big Query Virtual Schema

19 Jun 2019 | Share

Virtual Schema

Googling Exasol

As we mentioned in an earlier blog article, we offer the Cloud Wizard for our analytics database — so you can set up  your Exasol cluster in a matter of clicks on cloud platforms. This solution and our ready-to-use machine images were announced as part of our official support of the Google Cloud platform. With the addition of the Big Query SQL dialect to our Virtual Schemas, we now can also provide you with integration into one of Google’s popular SaaS services. Other services are on our roadmap and will follow suit.

Using Big Query as data source for Exasol

Regular tech blog readers will notice that the use case I am going to cover today is the same one I referenced in a recent article about connecting Exasol to AWS Athena.

This is what we are going to do:

  1. Set up a project on Google Cloud.
  2. Download a fun dataset from the public domain. That’s right, it’s UFO chasing time again!
  3. Upload the dataset to a bucket in Google Cloud Storage.
  4. Create the credentials necessary to connect to Big Query.
  5. Setup Exasol with a Virtual Schema for Big Query.
  6. Run a query through the Virtual Schema.

The Project is everything

Before you start following this tutorial, you first need a project in Google Cloud, as context for your setup. Unless you set up your very own Google Could account, projects will be under the control of your IT department — or with the administrator of your organization’s Google account.

If you happen to have administrative privileges, take a look at  Creating and Managing Projects in the Google Cloud Guides section. If not, ask your admin to create a project for you.

UFO hunting – the second wave of little green people

When I was looking for a public domain data set for an earlier article, I came across one about UFO sightings and chose it for my tutorials for two reasons: firstly because it is entertaining, secondly because the data set displays some of the typical data quality challenges everyone working in analytics has to face on a regular basis – like missing values or values that don’t match the data type of the column.

Please download the UFO sightings data set provided by the ‘NUFORC’ as a preparation.

Saucers in a bucket

Next, log into the Google Cloud Console and create a bucket for storing the data set.

If you’re new to the Google cloud, here is a short walk through for you:

  1. In the menu on the left section ‘Storage’ click ‘Storage’ → ‘Browser’.
  2. Click the ‘Create Bucket’ link.
  3. Give the bucket a name and write it down so that you remember it.
  4. For our example a regional bucket with bucket-level permission is sufficient, so choose those options.
  5. Click ‘Create’.
  6. Click the name of the newly created bucket in the list.
  7. Click ‘Upload files’.
  8. Pick the UFO data set and upload it.

At this point your bucket content should look like this:

Data set in Google bucket

Preparing Big Query

As a next step we’ll set up Big Query.

  1. Open the navigation menu on the left, and under ‘Big Data’ click ‘BigQuery
    (you have to scroll down the list quite a lot).
  2. In the BigQuery console you’ll see a list of resources on the left hand side.
  3. Select the name of the project created earlier.
  4. Click ‘CREATE DATASET’ on the right.
  5. In dialog ‘Create dataset’ by:
    1. Entering a dataset ID (in our example it’s ‘xp19ufos’).
    2. Choosing the data location – make sure it’s in the same region as the bucket created earlier.
    3. Choose ‘Never’ as the expiration date.
  6. Select the newly created dataset (below the project in the resource list on the left)
  7. Click ‘CREATE TABLE’.
  8. In dialog ‘Create table’ by:
    1. Selecting ‘Create table from’ : ‘Google Cloud Storage’.
    2. Browsing to the UFO dataset inside the bucket we created earlier.
    3. Choosing ‘CSV’ as the ‘File format’.
    4. Naming the table ‘ufos’.
    5. Choosing ‘No partitioning’.
    6. Adding the following type of fields for ‘STRING’: ‘observed’, ‘location’, ‘state’, ‘country’, ‘appearance’, ‘duration_seconds’, ‘duration’, ‘description’, ‘date_observed’, ‘latitude’ and ‘longitude’.
    7. Making sure all fields are nullable.

After these steps, Big Query knows the schema of you test dataset and where to find the raw data. Here is what your setup should look like:

Test dataset setup on Big Query

Test dataset setup on Big Query

As a simple validation run the following query in Big Query’s ‘Query editor’:

SELECT * FROM xp19ufos.ufos LIMIT 5;

The result will look like this:

A simple query in Big Query

A simple query in Big Query

Now that you know that Big Query is setup correctly, you can take the next step and get prepared to attach an Exasol Virtual Schema.

What’s the code word?

In order to access Big Query through a Virtual Schema, you need to authenticate against Big Query. For that you need to create a so called ‘service account’ and its credentials. Basically, this is a machine user account that accesses a Google service with a set of permissions assigned to it by an administrator.

To create a service account, follow these steps:

  1. Open the API & Services Dashboard by bringing up the menu and clicking ‘APIs & Services’ → ‘Dashboard’
  2. Click ‘Credentials’.
  3. Click ‘Create credentials’ (choose ‘Service Account Credentials’).
  4. In wizard ‘Create service account’ by:
    1. Entering a new service account name.
    2. Selecting ‘JSON’ as the key type.
    3. Selecting roles: ‘BigQuery Data Viewer’, ‘BigQuery Job User’ and ‘BigQueryMetadata Viewer’.
    4. Click ‘Create’. This automatically causes your browser to download the private key.

You will need the email address that identifies the service account as well as the downloaded private key later for connecting the Virtual Schema to Big Query.

Setting up everything in our analytics database

What you need here are the following things:

  1. A running Exasol cluster or single-host installation.
  2. The latest Virtual Schema JAR file.
  3. A JDBC driver for Big Query (pick the one that supports JDBC standard 4.2).

Installing our analytics database

Before can configure the Virtual Schema, you obviously need a running Exasol analytics database to install it on. You have three different options for this tutorial:

1. Reusing an existing Exasol analytics database installation

If you already installed a working database, you can skip this step. If not, you have two quick options.

2. Deploying Exasol on the Google Cloud using the Cloud Deployment Wizard

In case you want the full Google experience, I recommend starting up our Cloud Deployment Wizard and setting up a cluster on Google. Since that is a topic on its own and would make this tutorial too long, please refer to ‘Exasol on Google Cloud’ for more information.

As this is a tutorial we’re going to optimize our setup for the minimum possible costs by creating a single-node Exasol installation with the smallest possible instance type.

  1. Start the Cloud Deployment Wizard.
  2. Select ‘Google Cloud’.
  3. Select the region where you set up the bucket and Big Query.

    Cloud Deployment Wizzard for Google

    Cloud Deployment Wizzard for Google

  4. Click ‘Continue’.
  5. Click the ‘Advanced Configuration’ button.
  6. Select ‘Exasol Single Node’.
  7. Select the ‘Instance Family’ and ‘General Purpose’.
  8. Select the smallest instance type and model.

    Smallest single node setup on Google Cloud

    Smallest single node setup on Google Cloud

  9. Click ‘Continue’.
  10. Check the displayed summary.

    Google Cloud deployment summary

    Google Cloud deployment summary

  11. Click ‘create new VPC’.
  12. Choose one of the two deployment options: either directly via Google Cloud Shell or by downloading the Deployment Manager templates and executing them separately.

3. Running our Community Edition of the database

Your third option is to download the community edition of Exasol’s analytics database and install it on your local machine. The community edition is a size-limited, single-node setup of our analytics database. It’s perfectly fine for the purpose of this tutorial and comes at no extra cost.

Installing the Virtual Schema

No matter which installation option you picked, setting up the Virtual Schema is always the same. Just make sure that your Exasol analytics database is able to access the Big Query service. Check network and firewall settings in case the connection cannot be established.

Follow the steps described in the documentation of the BigQuery SQL dialect for Virtual Schemas to setup the Virtual Schema.

We regularly improve this documentation to make it more user-friendly, so I am deliberately not copying the instructions into this blog article.

Googling little green people through the Virtual Schema

Once you have the Virtual Schema setup ready, you can now access the UFO dataset through Big Query as if it were just a regular table — or rather a view — inside of Exasol.

The following query creates a ‘top five’ of UFO sightings, grouped by appearance. Sadly we can’t help you create an interstellar space ship. Well, at least not yet.

SELECT COUNT(1) AS "spot_count", "appearance"
FROM BIGQUERYTEST."ufos"
GROUP BY "appearance"
ORDER BY "spot_count"
LIMIT 5;

In the example BIGQUERYTEST is the name of the Virtual Schema and ufos the name of the virtual table, the CSV data is projected on.

Exasol’s native Google Could experience

As you saw, we now natively support the Google Cloud platform with Exasol’s Cloud Deployment Wizard, Big Query Virtual Schema and ready-to-use machine images.

Keep an eye on our roadmap to learn what’s up next on the Google platform.

10 trends impacting data analytics

Now that we’re well and truly in the age of data, what’s coming next? 

Free

Whitepaper