Create a Custom Column Pair Map Expectation

ColumnPairMapExpectations are a sub-type of ExpectationA verifiable assertion about data.. They are evaluated for a pair of columns and ask a yes/no question about the row-wise relationship between those two columns. Based on the result, they then calculate the percentage of rows that gave a positive answer. If the percentage is high enough, the Expectation considers that data valid.

This guide will walk you through the process of creating a custom ColumnPairMapExpectation.

Prerequisites

• Completion of the Quickstart.
• A configured and functional development environment.

Choose a name for your Expectation

First, decide on a name for your own Expectation. By convention, ColumnPairMapExpectations always start with expect_column_pair_values_. You can see other naming conventions in the Expectations section of the code Style Guide.

Your Expectation will have two versions of the same name: a CamelCaseName and a snake_case_name. For example, this tutorial will use:

• ExpectColumnPairValuesToHaveADifferenceOfThree
• expect_column_pair_values_to_have_a_difference_of_three

Copy and rename the template file

By convention, each Expectation is kept in its own python file, named with the snake_case version of the Expectation's name.

You can find the template file for a custom ColumnPairMapExpectation here. Download the file, place it in the appropriate directory, and rename it to the appropriate name.

cp column_pair_map_expectation_template.py /SOME_DIRECTORY/expect_column_pair_values_to_have_a_difference_of_three.py

Storing Expectation files

During development, you don't need to store Expectation files in a specific location. Expectation files are self-contained and can be executed anywhere as long as GX is installed However, to use your new Expectation with other GX components, you'll need to make sure the file is stored one of the following locations:

• If you're building a Custom ExpectationAn extension of the `Expectation` class, developed outside of the Great Expectations library. for personal use, you'll need to put it in the great_expectations/plugins/expectations folder of your GX deployment, and import your Custom Expectation from that directory whenever it will be used. When you instantiate the corresponding DataContext, it will automatically make all PluginsExtends Great Expectations' components and/or functionality. in the directory available for use.

• If you're building a Custom Expectation to contribute to the open source project, you'll need to put it in the repo for the Great Expectations library itself. Most likely, this will be within a package within contrib/: great_expectations/contrib/SOME_PACKAGE/SOME_PACKAGE/expectations/. To use these Expectations, you'll need to install the package.

For more information about Custom Expectations, see Use a Custom Expectation.

Generate a diagnostic checklist for your Expectation

Once you've copied and renamed the template file, you can execute it as follows.

python expect_column_pair_values_to_have_a_difference_of_three.py

The template file is set up so that this will run the Expectation's print_diagnostic_checklist() method. This will run a diagnostic script on your new Expectation, and return a checklist of steps to get it to full production readiness.

Completeness checklist for ExpectColumnPairValuesToMatchSomeCriteria:
  ✔ Has a valid library_metadata object
    Has a docstring, including a one-line short description that begins with "Expect" and ends with a period
    Has at least one positive and negative example case, and all test cases pass
    Has core logic and passes tests on at least one Execution Engine
    Passes all linting checks
    Has basic input validation and type checking
    Has both Statement Renderers: prescriptive and diagnostic
    Has core logic that passes tests for all applicable Execution Engines and SQL dialects
    Has a robust suite of tests, as determined by a code owner
    Has passed a manual review by a code owner for code standards and style guides

When in doubt, the next step to implement is the first one that doesn't have a ✔ next to it. This guide covers the first five steps on the checklist.

Change the Expectation class name and add a docstring

By convention, your MetricA computed attribute of data such as the mean of a column. class is defined first in a Custom Expectation. For now, we're going to skip to the Expectation class and begin laying the groundwork for the functionality of your Custom Expectation.

Let's start by updating your Expectation's name and docstring.

Replace the Expectation class name

class ExpectColumnPairValuesToMatchSomeCriteria(ColumnPairMapExpectation):

with your real Expectation class name, in upper camel case:

class ExpectColumnPairValuesToHaveADifferenceOfThree(ColumnPairMapExpectation):

You can also go ahead and write a new one-line docstring, replacing

"""TODO: Add a docstring here"""

with something like:

"""Expect two columns to have a row-wise difference of three."""

Make sure your one-line docstring begins with "Expect " and ends with a period. You'll also need to change the class name at the bottom of the file, by replacing this line:

ExpectColumnPairValuesToMatchSomeCriteria().print_diagnostic_checklist()

with this one:

ExpectColumnPairValuesToHaveADifferenceOfThree().print_diagnostic_checklist()

Later, you can go back and write a more thorough docstring. See Expectation Docstring Formatting.

At this point you can re-run your diagnostic checklist. You should see something like this:

$ python expect_column_pair_values_to_have_a_difference_of_three.py

Completeness checklist for ExpectColumnPairValuesToHaveADifferenceOfThree:
  ✔ Has a valid library_metadata object
  ✔ Has a docstring, including a one-line short description that begins with "Expect" and ends with a period
    Has at least one positive and negative example case, and all test cases pass
    Has core logic and passes tests on at least one Execution Engine
    Passes all linting checks
...

Congratulations! You're one step closer to implementing a Custom Expectation.

Add example cases

You're going to search for examples = [] in your file, and replace it with at least two test examples. These examples serve the following purposes:

• They provide test fixtures that Great Expectations can execute automatically with pytest.

• They help users understand the logic of your Expectation by providing tidy examples of paired input and output. If you contribute your Expectation to open source, these examples will appear in the Gallery.

Your examples will look similar to this example:

examples = [
    {
        "data": {
            "col_a": [3, 0, 1, 2, 3, 2],
            "col_b": [0, -3, 4, -1, 0, 1],
        },
        "tests": [
            {
                "title": "basic_positive_test",
                "exact_match_out": False,
                "include_in_gallery": True,
                "in": {"column_A": "col_a", "column_B": "col_b", "mostly": 0.8},
                "out": {
                    "success": True,
                },
            },
            {
                "title": "basic_negative_test",
                "exact_match_out": False,
                "include_in_gallery": True,
                "in": {"column_A": "col_a", "column_B": "col_b", "mostly": 1},
                "out": {
                    "success": False,
                },
            },
        ],
    }
]

Here's a quick overview of how to create test cases to populate examples. The overall structure is a list of dictionaries. Each dictionary has two keys:

• data: defines the input data of the example as a table/data frame. In this example the table has one column named col_a and a second column named col_b. Both columns have 6 rows. (Note: when you define multiple columns, make sure that they have the same number of rows.)
• tests: a list of test cases to ValidateThe act of applying an Expectation Suite to a Batch. against the data frame defined in the corresponding data.
  • title should be a descriptive name for the test case. Make sure to have no spaces.
  • include_in_gallery: This must be set to True if you want this test case to be visible in the Gallery as an example.
  • in contains exactly the parameters that you want to pass in to the Expectation. "in": {"column_A": "col_a", "column_B": "col_b", "mostly": 0.8} in the example above is equivalent to expect_column_pair_values_to_have_a_difference_of_three(column_A="col_a", column_B="col_b", mostly=0.8)
  • out is based on the Validation ResultGenerated when data is Validated against an Expectation or Expectation Suite. returned when executing the Expectation.
  • exact_match_out: if you set exact_match_out=False, then you don’t need to include all the elements of the Validation Result object - only the ones that are important to test.

If you run your Expectation file again, you won't see any new checkmarks, as the logic for your Custom Expectation hasn't been implemented yet. However, you should see that the tests you've written are now being caught and reported in your checklist:

$ python expect_column_pair_values_to_have_a_difference_of_three.py

Completeness checklist for ExpectColumnPairValuesToHaveADifferenceOfThree:
  ✔ Has a valid library_metadata object
  ✔ Has a docstring, including a one-line short description that begins with "Expect" and ends with a period
...
    Has core logic that passes tests for all applicable Execution Engines and SQL dialects
          Only 0 / 2 tests for pandas are passing
          Failing: basic_positive_test, basic_negative_test
...

note

For more information on tests and example cases,
see our guide on how to create example cases for a Custom Expectation.

Implement your Metric and connect it to your Expectation

This is the stage where you implement the actual business logic for your Expectation.

To do so, you'll need to implement a function within a Metric, and link it to your Expectation. By the time your Expectation is complete, your Metric will have functions for all three Execution EnginesA system capable of processing data to compute Metrics. (Pandas, Spark, & SQLAlchemy) supported by Great Expectations. For now, we're only going to define one.

note

Metrics answer questions about your data posed by your Expectation,
and allow your Expectation to judge whether your data meets your expectations.

Your Metric function will have the @column_pair_condition_partial decorator, with the appropriate engine. Metric functions can be as complex as you like, but they're often very short. For example, here's the definition for a Metric function to calculate whether the difference between the values in two columns equals 3 using the PandasExecutionEngine.

@column_pair_condition_partial(engine=PandasExecutionEngine)
def _pandas(cls, column_A, column_B, **kwargs):
    return abs(column_A - column_B) == 3

This is all that you need to define for now. The ColumnMapMetricProvider and ColumnMapExpectation classes have built-in logic to handle all the machinery of data validation, including standard parameters like mostly, generation of Validation Results, etc.

Other parameters

Expectation Success Keys - A tuple consisting of values that must / could be provided by the user and defines how the Expectation evaluates success.

Expectation Default Kwarg Values (Optional) - Default values for success keys and the defined domain, among other values.

Metric Condition Value Keys (Optional) - Contains any additional arguments passed as parameters to compute the Metric.

Next, choose a Metric Identifier for your Metric. By convention, Metric Identifiers for Column Pair Map Expectations start with column_pair_values.. The remainder of the Metric Identifier simply describes what the Metric computes, in snake case. For this example, we'll use column_pair_values.diff_three.

You'll need to substitute this metric into two places in the code. First, in the Metric class, replace

condition_metric_name = "METRIC NAME GOES HERE"

with

condition_metric_name = "column_pair_values.diff_three"

Second, in the Expectation class, replace

map_metric = "METRIC NAME GOES HERE"

with

map_metric = "column_pair_values.diff_three"

It's essential to make sure to use matching Metric Identifier strings across your Metric class and Expectation class. This is how the Expectation knows which Metric to use for its internal logic.

Finally, rename the Metric class name itself, using the camel case version of the Metric Identifier, minus any periods.

For example, replace:

class ColumnPairValuesMatchSomeCriteria(ColumnPairMapMetricProvider):

with

class ColumnPairValuesDiffThree(ColumnPairMapMetricProvider):

Running your diagnostic checklist at this point should return something like this:

$ python expect_column_pair_values_to_have_a_difference_of_three.py

Completeness checklist for ExpectColumnPairValuesToHaveADifferenceOfThree:
  ✔ Has a valid library_metadata object
  ✔ Has a docstring, including a one-line short description that begins with "Expect" and ends with a period
  ✔ Has at least one positive and negative example case, and all test cases pass
  ✔ Has core logic and passes tests on at least one Execution Engine
    Passes all linting checks
...

Linting

Finally, we need to lint our now-functioning Custom Expectation. Our CI system will test your code using black, and ruff.

If you've set up your dev environment as recommended in the Prerequisites, these libraries will already be available to you, and can be invoked from your command line to automatically lint your code:

black <PATH/TO/YOUR/EXPECTATION.py>
ruff <PATH/TO/YOUR/EXPECTATION.py> --fix

info

If desired, you can automate this to happen at commit time. See our guidance on linting for more on this process.

Once this is done, running your diagnostic checklist should now reflect your Custom Expectation as meeting our linting requirements:

$ python expect_column_pair_values_to_have_a_difference_of_three.py

Completeness checklist for ExpectColumnPairValuesToHaveADifferenceOfThree:
  ✔ Has a valid library_metadata object
  ✔ Has a docstring, including a one-line short description that begins with "Expect" and ends with a period
  ✔ Has at least one positive and negative example case, and all test cases pass
  ✔ Has core logic and passes tests on at least one Execution Engine
  ✔ Passes all linting checks
...

note

If you've already built a Custom Column Aggregate Expectation, you may notice that we didn't implement a _validate method here. While we have to explicitly create this functionality for Column Aggregate Expectations, Column Map Expectations come with that functionality built in; no extra _validate needed!

Contribute (Optional)

This guide will leave you with a Custom Expectation sufficient for contribution to Great Expectations at an Experimental level.

If you plan to contribute your Expectation to the public open source project, you should update the library_metadata object before submitting your Pull Request. For example:

library_metadata = {
    "tags": [],  # Tags for this Expectation in the Gallery
    "contributors": [  # Github handles for all contributors to this Expectation.
        "@your_name_here",  # Don't forget to add your github handle here!
    ],
}

would become

library_metadata = {
    "tags": [
        "basic math",
        "multi-column expectation",
    ],
    "contributors": ["@joegargery"],
}

This is particularly important because we want to make sure that you get credit for all your hard work!

note

For more information on our code standards and contribution, see our guide on Levels of Maturity for Expectations.

To view the full script used in this page, see it on GitHub:

• expect_column_pair_values_to_have_a_difference_of_three.py