# Can ColumnPairMapExpectations handle row\_conditions?

**URL:** <https://discourse.greatexpectations.io/t/can-columnpairmapexpectations-handle-row-conditions/1793>\
**Category:** GX Core Support\
**Created:** [July 4, 2024, 9:51am UTC](https://discourse.greatexpectations.io/t/can-columnpairmapexpectations-handle-row-conditions/1793 "2024-07-04T09:51:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mike\_f50](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.greatexpectations.io/mike_f50/32/169_2.png) [@mike\_f50](https://discourse.greatexpectations.io/u/mike_f50)\
**Post date:** [July 4, 2024, 9:51am UTC](https://discourse.greatexpectations.io/t/can-columnpairmapexpectations-handle-row-conditions/1793/1 "2024-07-04T09:51:45Z")

</div>

I am validating some data with a `ValueString` coumn and a `ValueInt` column.

When `ValueString` is populated, I expect it to correspond to the `ValueInt`. (In the data, this happens for specific values, e.g. `ValueString` of `">90"` with `VallueInt` of `90`.) When `ValueString` is `null`, `ValueInt` can be whatever it wants.

I have tried to achieve this via an `expect_column_pair_values_to_be_in_set` expectation with a `row_condition`, configured as follows:

```json
{
  "column_A": "ValueString",
  "column_B": "ValueInt",
  "condition_parser": "spark",
  "row_condition": "ValueString IS NOT NULL",
  "value_pairs_set": [[">90", 90], [">60", 60], [">140", 140], [">=90", 90] ]
}

```

However, the data docs rendering is failing with:

> Invalid result values were found when trying to instantiate an ExpectationValidationResult. - Invalid result values are likely caused by inconsistent cache values. - Great Expectations enables caching by default. - Please ensure that caching behavior is consistent between the underlying Dataset (e.g. Spark) and Great Expectations. Result: { **“element\_count”: 14777** , **“unexpected\_count”: 50065** , “unexpected\_percent”: 77.21075845902348, “partial\_unexpected\_list”: [[ null, 75], [null, 160], [null, 82], [null, 53], [null, 69], …

My obersavtions:

1. The error message is coming through consistently, so I think the suggestion of a cause relating to caching is a red herring.
2. The `element_count` is smaller than the `unexpected_count`.
3. The `element_count` corresponds to the number of records passing the `row_condition`.
4. The `partial_unexpected_list` shows examples which should fail the `row_condition`.

Hence my question: Is there something about `ColumnPairMapExpectations`, or `expect_column_pair_values_to_be_in_set` specifically, being incompatible with `row_condition`s?

Reviewing the validations store, the expectation failed, with no result, so the exception is occurring during validation and not just during data docs rendering.

---

<div class="post-metadata">

**Author:** ![mike\_f50](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.greatexpectations.io/mike_f50/32/169_2.png) [@mike\_f50](https://discourse.greatexpectations.io/u/mike_f50)\
**Post date:** [July 4, 2024, 6:19pm UTC](https://discourse.greatexpectations.io/t/can-columnpairmapexpectations-handle-row-conditions/1793/2 "2024-07-04T18:19:42Z")

</div>

I have discovered a workaround.

Instead of a `row_condition`, it’s possible to use `ignore_row_if`. This does not seem to be well documented. (The best information I found was on this [issue](https://github.com/great-expectations/great_expectations/issues/9748).) However, the following is doing what I require:

```auto
{
  "column_A": "ValueString",
  "column_B": "ValueInt",
  "condition_parser": "spark",
  "ignore_row_if": "either_value_is_missing",
  "value_pairs_set": [[">90", 90], [">60", 60], [">140", 140], [">=90", 90] ]
}

```

I would still be interested to know whether this should have been possible with a `row_condition`, if anyone knows.