Merge remote-tracking branch 'great-expectations/develop' into develop

Author: fredwang1012

.github/workflows/ci.yml

@@ -635,7 +635,8 @@ jobs:
       fail-fast: false
       matrix:
         markers:
-          - athena or openpyxl or pyarrow or project or sqlite or aws_creds
+          - openpyxl or pyarrow or project or sqlite or aws_creds
+          - athena
           - aws_deps
           - big
           - bigquery

docs/docusaurus/docs/cloud/connect/connect_databrickssql.md

@@ -35,7 +35,7 @@ import Tabs from '@theme/Tabs';
 
 6. Click **Add x Asset(s)**.
 
-7. Decide which [Anomaly Detection](/docs/cloud/overview/accelerating_test_coverage.md#anomaly-detection) options you want to enable. By default, GX Cloud adds [warning-severity](/docs/cloud/expectations/expectations_overview.md#failure-severity) Expectations to detect **Schema**, **Volume**, and **Completeness** anomalies. You can de-select recommendations you’d like to opt out of.
+7. Decide which [Anomaly Detection](/docs/cloud/overview/accelerating_test_coverage.md#anomaly-detection) options you want to enable. By default, GX Cloud adds [warning-severity](/docs/cloud/expectations/expectations_overview.md#failure-severity) Expectations to detect **Schema** and **Volume** anomalies. You can de-select recommendations you’d like to opt out of. You can choose to generate Expectations to detect **Completeness** anomalies.
 
 8. Click **Start monitoring** or **Finish**.
 

docs/docusaurus/docs/cloud/connect/connect_postgresql.md

@@ -60,7 +60,7 @@ import Tabs from '@theme/Tabs';
 
 6. Click **Add x Asset(s)**.
 
-7. Decide which [Anomaly Detection](/docs/cloud/overview/accelerating_test_coverage.md#anomaly-detection) options you want to enable. By default, GX Cloud adds [warning-severity](/docs/cloud/expectations/expectations_overview.md#failure-severity) Expectations to detect **Schema**, **Volume**, and **Completeness** anomalies. You can de-select recommendations you’d like to opt out of.
+7. Decide which [Anomaly Detection](/docs/cloud/overview/accelerating_test_coverage.md#anomaly-detection) options you want to enable. By default, GX Cloud adds [warning-severity](/docs/cloud/expectations/expectations_overview.md#failure-severity) Expectations to detect **Schema** and **Volume** anomalies. You can de-select recommendations you’d like to opt out of. You can choose to generate Expectations to detect **Completeness** anomalies.
 
 8. Click **Start monitoring** or **Finish**.
 

docs/docusaurus/docs/cloud/connect/connect_redshift.md

@@ -101,7 +101,7 @@ Run all queries in the [Amazon Redshift query editor v2](https://docs.aws.amazon
 
 7. Click **Add x Asset(s)**.
 
-8. Decide which [Anomaly Detection](/docs/cloud/overview/accelerating_test_coverage.md#anomaly-detection) options you want to enable. By default, GX Cloud adds [warning-severity](/docs/cloud/expectations/expectations_overview.md#failure-severity) Expectations to detect **Schema**, **Volume**, and **Completeness** anomalies. You can de-select recommendations you’d like to opt out of.
+8. Decide which [Anomaly Detection](/docs/cloud/overview/accelerating_test_coverage.md#anomaly-detection) options you want to enable. By default, GX Cloud adds [warning-severity](/docs/cloud/expectations/expectations_overview.md#failure-severity) Expectations to detect **Schema** and **Volume** anomalies. You can de-select recommendations you’d like to opt out of. You can choose to generate Expectations to detect **Completeness** anomalies.
 
 9. Click **Start monitoring** or **Finish**.
 

docs/docusaurus/docs/cloud/connect/connect_snowflake.md

@@ -112,7 +112,7 @@ Then, you can use the GX Cloud UI to [add a Data Asset](/cloud/data_assets/manag
 
 7. Click **Add x Asset(s)**.
 
-8. Decide which [Anomaly Detection](/docs/cloud/overview/accelerating_test_coverage.md#anomaly-detection) options you want to enable. By default, GX Cloud adds [warning-severity](/docs/cloud/expectations/expectations_overview.md#failure-severity) Expectations to detect **Schema**, **Volume**, and **Completeness** anomalies. You can de-select recommendations you’d like to opt out of.
+8. Decide which [Anomaly Detection](/docs/cloud/overview/accelerating_test_coverage.md#anomaly-detection) options you want to enable. By default, GX Cloud adds [warning-severity](/docs/cloud/expectations/expectations_overview.md#failure-severity) Expectations to detect **Schema** and **Volume** anomalies. You can de-select recommendations you’d like to opt out of. You can choose to generate Expectations to detect **Completeness** anomalies.
 
 9. Click **Start monitoring** or **Finish**.
 

docs/docusaurus/docs/cloud/data_assets/manage_data_assets.md

@@ -24,7 +24,7 @@ To add a Data Asset from an existing Data Source, complete the following steps:
 
 4. Click **Add x Asset(s)**.
 
-5. Decide which [Anomaly Detection](/docs/cloud/overview/accelerating_test_coverage.md#anomaly-detection) options you want to enable. By default, GX Cloud adds [warning-severity](/docs/cloud/expectations/expectations_overview.md#failure-severity) Expectations to detect **Schema**, **Volume**, and **Completeness** anomalies. You can de-select recommendations you’d like to opt out of.
+5. Decide which [Anomaly Detection](/docs/cloud/overview/accelerating_test_coverage.md#anomaly-detection) options you want to enable. By default, GX Cloud adds [warning-severity](/docs/cloud/expectations/expectations_overview.md#failure-severity) Expectations to detect **Schema** and **Volume** anomalies. You can de-select recommendations you’d like to opt out of. You can choose to generate Expectations to detect **Completeness** anomalies.
 
 6. Click **Start monitoring** or **Finish**.
 

docs/docusaurus/docs/cloud/expectations/expectations_overview.md

@@ -176,9 +176,9 @@ Here is a comparison of key characteristics of GX-managed and API-managed Expect
 |--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | Edit               | [Edit parameters](/cloud/expectations/manage_expectations.md#edit-an-expectation) with the GX Cloud UI                                                                                              | [Edit parameters with the GX Cloud API](/reference/api/expectations/Expectation_class.mdx) or the GX Cloud UI                                                                                                                                                                                                                        |
 | Batch              | [Define a Batch](/cloud/expectations/manage_expectations.md#optional-define-a-batch) in the GX Cloud UI                                                                                                | Define a Batch with the GX Cloud API when connecting to [SQL](/core/connect_to_data/sql_data/sql_data.md#create-a-batch-definition), [filesystem](/core/connect_to_data/filesystem_data/filesystem_data.md#create-a-batch-definition), or [dataframe](/core/connect_to_data/dataframes/dataframes.md#create-a-batch-definition) data |
-| Validate           | [Run a Validation](/docs/cloud/validations/manage_validations.md#run-a-validation) using the GX Cloud UI or [run a Checkpoint](/core/trigger_actions_based_on_results/run_a_checkpoint.md) with the GX Cloud API | [Create a Validation Definition and run it](/core/run_validations/run_validations.md) with the GX Cloud API                                                                                                                                                                                                                          |
+| Ad hoc Validation  | [Run a Validation](/docs/cloud/validations/manage_validations.md#run-a-validation) using the GX Cloud UI or [run a Checkpoint](/core/trigger_actions_based_on_results/run_a_checkpoint.md) with the GX Cloud API | [Create a Validation Definition and run it](/core/run_validations/run_validations.md) with the GX Cloud API                                                                                                                                                                                                                          |
+| Recurring Validations | [Schedule Validations](/cloud/schedules/manage_schedules.md) in the GX Cloud UI                                                                                                      | Not supported, use an [orchestrator](/cloud/connect/connect_airflow.md) to control recurring validations                                                                                                                                                                                                                    |
 | Validation Results | [Access results in the Validations tab](/cloud/validations/manage_validations.md#view-validation-run-history) of the GX Cloud UI                                                                       | [Access results with the GX Cloud API](/core/trigger_actions_based_on_results/choose_a_result_format/choose_a_result_format.md) or in the Validations tab of the GX Cloud UI                                                                                                                                                            |
-| Schedule           | Keep default schedule or [edit schedule](/cloud/schedules/manage_schedules.md) in the GX Cloud UI                                                                                                      | Not supported, use an [orchestrator](/cloud/connect/connect_airflow.md) to control recurring validations                                                                                                                                                                                                                    |
 | Expectation Suite  | Automatically organized in a hidden default Expectation Suite                                                                                                                                       | Manually grouped into [custom Expectation Suites](/core/define_expectations/organize_expectation_suites.md) via the GX Cloud API                                                                                                                                                                                                     |
 | Delete             | [Delete Expectation](/docs/cloud/expectations/manage_expectations/#delete-an-expectation) with the GX Cloud UI                                                                                         | [Delete Expectation with the GX Cloud API](/reference/api/ExpectationSuite_class.mdx#great_expectations.ExpectationSuite.delete_expectation) or the GX Cloud UI                                                                                                                                                                         |
 

docs/docusaurus/docs/cloud/expectations/manage_expectations.md

@@ -32,11 +32,13 @@ This page provides instructions for working with Expectations. To learn about Ex
 
 5. Select an Expectation type.
 
-6. Complete the mandatory and optional fields for the Expectation. A recurring [validation schedule](/cloud/schedules/manage_schedules.md) will be applied automatically to your Expectation. 
+6. Complete the mandatory and optional fields for the Expectation.
 
 7. Click **Save** or click **Save & Add More** and then repeat steps 4 through 7 to add additional Expectations.
 
-8. Optional. Run a Validation. See [Run a Validation](/cloud/validations/manage_validations.md#run-a-validation).
+8. Optional. Run an ad hoc Validation. See [Run a Validation](/cloud/validations/manage_validations.md#run-a-validation).
+
+9. Optional. Configure recurring Validations. See [Manage schedules](/docs/cloud/schedules/manage_schedules).
 
 
 ## Save time with ExpectAI <span class="beta">Beta</span>

docs/docusaurus/docs/cloud/overview/accelerating_test_coverage.md

@@ -11,7 +11,7 @@ GX Cloud provides several conveniences to help you more quickly achieve test cov
 
 ## Anomaly Detection
 
-When you [add a new Data Asset](/cloud/data_assets/manage_data_assets.md), GX Cloud by default generates Expectations to detect anomalies in the following data quality issues. You can also automate Anomaly Detection for these when you [add Expectations](/cloud/expectations/manage_expectations.md#add-an-expectation) for an existing Data Asset.
+When you [add a new Data Asset](/cloud/data_assets/manage_data_assets.md), you can have GX Cloud generate Expectations to detect anomalies in the following data quality issues. You can also automate Anomaly Detection for these when you [add Expectations](/cloud/expectations/manage_expectations.md#add-an-expectation) for an existing Data Asset.
 
 - [Schema](#schema)
 - [Volume](#volume)
@@ -22,16 +22,16 @@ When you [add a new Data Asset](/cloud/data_assets/manage_data_assets.md), GX Cl
 
 ### Schema
 
-To detect schema anomalies, we automatically generate a rule to [**expect table columns to match set**](/reference/learn/data_quality_use_cases/schema.md#expect-table-columns-to-match-set) using the Data Asset’s initial columns as the set to match. If the number or names of columns in the Data Asset change, this Expectation will fail.
+To detect schema anomalies, we generate a rule to [**expect table columns to match set**](/reference/learn/data_quality_use_cases/schema.md#expect-table-columns-to-match-set) using the Data Asset’s initial columns as the set to match. If the number or names of columns in the Data Asset change, this Expectation will fail.
 
 ### Volume
 
-To detect anomalies in row count, we automatically generate a rule to [**expect table row count to be between**](/reference/learn/data_quality_use_cases/volume.md#expect-table-row-count-to-be-between) a forecasted range that tests that the current validation run doesn’t deviate significantly from historical patterns. For example, if there is a sudden increase when volume has been stable or stagnation in a season when volume typically grows, then this Expectation will fail.
+To detect anomalies in row count, we generate a rule to [**expect table row count to be between**](/reference/learn/data_quality_use_cases/volume.md#expect-table-row-count-to-be-between) a forecasted range that tests that the current validation run doesn’t deviate significantly from historical patterns. For example, if there is a sudden increase when volume has been stable or stagnation in a season when volume typically grows, then this Expectation will fail.
 
 
 ### Completeness
 
-To detect completeness anomalies, we automatically generate rules for every column to [**expect column proportion of non-null values to be between**](/reference/learn/data_quality_use_cases/missingness.md#expect-column-proportion-of-non-null-values-to-be-between) a forecasted range that depends on the column's initial proportion of non-null values.
+To detect completeness anomalies, we generate rules for every column to [**expect column proportion of non-null values to be between**](/reference/learn/data_quality_use_cases/missingness.md#expect-column-proportion-of-non-null-values-to-be-between) a forecasted range that depends on the column's initial proportion of non-null values.
 
 - If a column initially has no null values, GX Cloud generates a rule to test that the column continues to have no null values.
 - If a column initially has all null values, GX Cloud generates a rule to test that the column continues to have all null values.

docs/docusaurus/docs/cloud/schedules/manage_schedules.md

@@ -4,13 +4,29 @@ title: 'Manage schedules'
 description: Create and manage schedules for Validations in GX Cloud.
 ---
 
-Use a schedule to automate data quality checks with GX-managed Expectations. When you add your first Expectation in the GX Cloud UI for a Data Asset, including when you choose to auto-generate Expectations for Anomaly Detection, we enable a default schedule for that Asset's GX-managed Expectations. By default, GX-managed Expectations are scheduled to run every 24 hours. The first run will be at the start of the next hour after you add your first Expectation in the Cloud UI. You can keep the default schedule, edit it, or disable it.
+Use a schedule to automate data quality checks with GX-managed Expectations.
 
 :::note Schedules are for GX-managed Expectations only
 To automate data quality checks for [API-managed Expectations](/cloud/expectations/manage_expectations.md#gx-managed-vs-api-managed-expectations), use an [orchestrator](/cloud/connect/connect_airflow.md).
 :::
 
 
+## Enable a schedule
+
+1. In GX Cloud, select the relevant **Workspace** and then click **Data Assets**.
+
+2. In the **Data Assets** list, click the Data Asset name.
+
+3. Next to **No scheduled validation**, click <img src="/img/pencil.png" alt="pencil icon" width="20" height="20"/> **Edit schedule**.
+
+4. Turn the Validation schedule **ON**.
+
+5. Select a **Frequency**.
+
+6. Select a **Start time** for the first run of the new schedule.
+
+7. Click **Save**.
+
 ## Edit a schedule
 
 1. In GX Cloud, select the relevant **Workspace** and then click **Data Assets**.