Skip to main content
Version: 0.15.50

How to connect to data on GCS using Spark

This guide will help you connect to your data stored on Google Cloud Storage (GCS) using Spark. This will allow you to ValidateThe act of applying an Expectation Suite to a Batch. and explore your data.

Prerequisites: This how-to guide assumes you have:
  • Completed the Getting Started Tutorial
  • A working installation of Great Expectations
  • Have access to data on a GCS bucket
  • Have access to a working Spark installation


1. Choose how to run the code in this guide

Get an environment to run the code in this guide. Please choose an option below.

If you use the Great Expectations CLICommand Line Interface, run this command to automatically generate a pre-configured Jupyter Notebook. Then you can follow along in the YAML-based workflow below:

great_expectations datasource new

2. Instantiate your project's DataContext

Import these necessary packages and modules.

import great_expectations as gx
from great_expectations.core.batch import Batch, BatchRequest, RuntimeBatchRequest
from great_expectations.data_context.types.base import (
from great_expectations.util import get_context

Please proceed only after you have instantiated your DataContext.

3. Configure your Datasource

Using this example configuration, add in your GCS bucket and path to a directory that contains some of your data:

datasource_yaml = rf"""
name: my_gcs_datasource
class_name: Datasource
class_name: SparkDFExecutionEngine
class_name: RuntimeDataConnector
- default_identifier_name
class_name: InferredAssetGCSDataConnector
bucket_or_name: <your_gcs_bucket_here>
prefix: <bucket_path_to_data>
pattern: (.*)\.csv
- data_asset_name

It is also important to note that GCS DataConnector for Spark supports the method of authentication that requires running the gcloud command line tool in order to obtain the GOOGLE_APPLICATION_CREDENTIALS environment variable.

For more details regarding storing credentials for use with Great Expectations see: How to configure credentials

For more details regarding authentication, please visit the following:

Run this code to test your configuration.


If you specified a GCS path containing CSV files you will see them listed as Available data_asset_names in the output of test_yaml_config().

Feel free to adjust your configuration and re-run test_yaml_config() as needed.

4. Save the Datasource configuration to your DataContext

Save the configuration into your DataContext by using the add_datasource() function.


5. Test your new Datasource

Verify your new DatasourceProvides a standard API for accessing and interacting with data from a wide variety of source systems. by loading data from it into a ValidatorUsed to run an Expectation Suite against data. using a Batch RequestProvided to a Datasource in order to create a Batch..

Add the GCS path to your CSV in the path key under runtime_parameters in your RuntimeBatchRequest.

batch_request = RuntimeBatchRequest(
datasource_name="version-0.15.50 my_gcs_datasource",
data_connector_name="version-0.15.50 default_runtime_data_connector_name",
data_asset_name="version-0.15.50 <your_meangingful_name>", # this can be anything that identifies this data_asset for you
runtime_parameters={"path": "<path_to_your_data_here>"}, # Add your GCS path here.
batch_identifiers={"default_identifier_name": "default_identifier"},

Then load data into the Validator.

context.add_or_update_expectation_suite(expectation_suite_name="version-0.15.50 test_suite")
validator = context.get_validator(
batch_request=batch_request, expectation_suite_name="version-0.15.50 test_suite"

🚀🚀 Congratulations! 🚀🚀 You successfully connected Great Expectations with your data.

Additional Notes

To view the full scripts used in this page, see them on GitHub:

Next Steps

Now that you've connected to your data, you'll want to work on these core skills: