google-pso-data-validator 6.3.0__tar.gz → 7.0.0__tar.gz

{google_pso_data_validator-6.3.0 → google_pso_data_validator-7.0.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: google-pso-data-validator
-Version: 6.3.0
+Version: 7.0.0
 Summary: A package to enable easy data validation
 Author: PSO DVT Engineering team
 Author-email: data-validator-eng@google.com
@@ -154,7 +154,7 @@ data-validation
   [--std COLUMNS]       Comma separated list of columns for stddev_samp or * for all numeric
   [--exclude-columns or -ec]
                         Flag to indicate the list of columns provided should be excluded and not included.
-  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE]
+  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE or CONNECTION_NAME.DATASET.TABLE]
                         BigQuery destination for validation results. Defaults to stdout.
                         See: *Validation Reports* section
   [--service-account or -sa PATH_TO_SA_KEY]
@@ -197,17 +197,16 @@ In addition, please note that SHA256 is not a supported function on Teradata sys
 If you wish to perform this comparison on Teradata you will need to
 [deploy a UDF to perform the conversion](https://github.com/akuroda/teradata-udf-sha2/blob/master/src/sha256.c).)
 
-Below is the command syntax for row validations. In order to run row level
-validations you need to pass a `--primary-key` flag which defines what field(s)
-the validation will be compared on, as well as either the `--comparison-fields` flag
-or the `--hash` flag. See *Primary Keys* section
+Below is the command syntax for row validations. In order to run row level validations we require
+unique columns to join row sets, which are either inferred from the source/target table or provided
+via the `--primary-keys` flag, and either the `--hash`, `--concat` or `--comparison-fields` flags.
+See *Primary Keys* section.
 
 The `--comparison-fields` flag specifies the values (e.g. columns) whose raw values will be compared
 based on the primary key join. The `--hash` flag will run a checksum across specified columns in
 the table. This will include casting to string, sanitizing the data (ifnull, rtrim, upper), concatenating,
 and finally hashing the row.
 
-
 Under the hood, row validation uses
 [Calculated Fields](https://github.com/GoogleCloudPlatform/professional-services-data-validator#calculated-fields) to
 apply functions such as IFNULL() or RTRIM(). These can be edited in the YAML or JSON config file to customize your row validation.
@@ -229,16 +228,17 @@ data-validation
                         Comma separated list of tables in the form schema.table=target_schema.target_table
                         Target schema name and table name are optional.
                         i.e 'bigquery-public-data.new_york_citibike.citibike_trips'
-  --primary-keys or -pk PRIMARY_KEYS
-                        Comma separated list of columns to use as primary keys.  See *Primary Keys* section
   --comparison-fields or -comp-fields FIELDS
                         Comma separated list of columns to compare. Can either be a physical column or an alias
                         See: *Calculated Fields* section for details
   --hash COLUMNS        Comma separated list of columns to hash or * for all columns
   --concat COLUMNS      Comma separated list of columns to concatenate or * for all columns (use if a common hash function is not available between databases)
+  [--primary-keys PRIMARY_KEYS, -pk PRIMARY_KEYS]
+                        Comma separated list of primary key columns, when not specified the value will be inferred
+                        from the source or target table if available.  See *Primary Keys* section
   [--exclude-columns or -ec]
                         Flag to indicate the list of columns provided should be excluded from hash or concat instead of included.
-  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE]
+  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE or CONNECTION_NAME.DATASET.TABLE]
                         BigQuery destination for validation results. Defaults to stdout.
                         See: *Validation Reports* section
   [--service-account or -sa PATH_TO_SA_KEY]
@@ -303,8 +303,6 @@ data-validation
                         Either --tables-list or --source-query (or file) and --target-query (or file) must be provided
   --target-query-file TARGET_QUERY_FILE, -tqf TARGET_QUERY_FILE
                         File containing the target sql command. Supports GCS and local paths.
-  --primary-keys PRIMARY_KEYS, -pk PRIMARY_KEYS
-                        Comma separated list of primary key columns 'col_a,col_b'.  See *Primary Keys* section
   --comparison-fields or -comp-fields FIELDS
                         Comma separated list of columns to compare. Can either be a physical column or an alias
                         See: *Calculated Fields* section for details
@@ -318,7 +316,10 @@ data-validation
   --partition-num INT, -pn INT
                         Number of partitions into which the table should be split, e.g. 1000 or 10000
                         In case this value exceeds the row count of the source/target table, it will be decreased to max(source_row_count, target_row_count)
-  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE]
+  [--primary-keys PRIMARY_KEYS, -pk PRIMARY_KEYS]
+                        Comma separated list of primary key columns, when not specified the value will be inferred
+                        from the source or target table if available.  See *Primary Keys* section
+  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE or CONNECTION_NAME.DATASET.TABLE]
                         BigQuery destination for validation results. Defaults to stdout.
                         See: *Validation Reports* section
   [--service-account or -sa PATH_TO_SA_KEY]
@@ -364,7 +365,7 @@ data-validation
                         Comma separated list of tables in the form schema.table=target_schema.target_table. Or shorthand schema.* for all tables.
                         Target schema name and table name are optional.
                         e.g.: 'bigquery-public-data.new_york_citibike.citibike_trips'
-  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE]
+  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE or CONNECTION_NAME.DATASET.TABLE]
                         BigQuery destination for validation results. Defaults to stdout.
                         See: *Validation Reports* section
   [--service-account or -sa PATH_TO_SA_KEY]
@@ -424,7 +425,7 @@ data-validation
   [--std COLUMNS]       Comma separated list of columns for stddev_samp or * for all numeric
   [--exclude-columns or -ec]
                         Flag to indicate the list of columns provided should be excluded and not included.
-  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE]
+  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE or CONNECTION_NAME.DATASET.TABLE]
                         BigQuery destination for validation results. Defaults to stdout.
                         See: *Validation Reports* section
   [--service-account or -sa PATH_TO_SA_KEY]
@@ -489,11 +490,11 @@ data-validation
   --hash '*'            '*' to hash all columns.
   --concat COLUMNS      Comma separated list of columns to concatenate or * for all columns
                         (use if a common hash function is not available between databases)
-  --primary-key or -pk JOIN_KEY
-                       Common column between source and target tables for join
+  [--primary-keys PRIMARY_KEYS, -pk PRIMARY_KEYS]
+                       Common column between source and target queries for join
   [--exclude-columns or -ec]
                         Flag to indicate the list of columns provided should be excluded from hash or concat instead of included.
-  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE]
+  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE or CONNECTION_NAME.DATASET.TABLE]
                         BigQuery destination for validation results. Defaults to stdout.
                         See: *Validation Reports* section
   [--service-account or -sa PATH_TO_SA_KEY]
@@ -720,6 +721,8 @@ In many cases, validations (e.g. count, min, max etc) produce one row per table.
 and target table is to compare the value for each column in the source with the value of the column in the target.
 `grouped-columns` validation and `validate row` produce multiple rows per table. Data Validation Tool needs one or more columns to uniquely identify each row so the source and target can be compared. Data Validation Tool refers to these columns as primary keys. These do not need to be primary keys in the table. The only requirement is that the keys uniquely identify the row in the results.
 
+These columns are inferred, where possible, from the source/target table or can be provided via the `--primary-keys` flag.
+
 ### Grouped Columns
 
 Grouped Columns contain the fields you want your aggregations to be broken out

{google_pso_data_validator-6.3.0 → google_pso_data_validator-7.0.0}/README.md

@@ -113,7 +113,7 @@ data-validation
   [--std COLUMNS]       Comma separated list of columns for stddev_samp or * for all numeric
   [--exclude-columns or -ec]
                         Flag to indicate the list of columns provided should be excluded and not included.
-  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE]
+  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE or CONNECTION_NAME.DATASET.TABLE]
                         BigQuery destination for validation results. Defaults to stdout.
                         See: *Validation Reports* section
   [--service-account or -sa PATH_TO_SA_KEY]
@@ -156,17 +156,16 @@ In addition, please note that SHA256 is not a supported function on Teradata sys
 If you wish to perform this comparison on Teradata you will need to
 [deploy a UDF to perform the conversion](https://github.com/akuroda/teradata-udf-sha2/blob/master/src/sha256.c).)
 
-Below is the command syntax for row validations. In order to run row level
-validations you need to pass a `--primary-key` flag which defines what field(s)
-the validation will be compared on, as well as either the `--comparison-fields` flag
-or the `--hash` flag. See *Primary Keys* section
+Below is the command syntax for row validations. In order to run row level validations we require
+unique columns to join row sets, which are either inferred from the source/target table or provided
+via the `--primary-keys` flag, and either the `--hash`, `--concat` or `--comparison-fields` flags.
+See *Primary Keys* section.
 
 The `--comparison-fields` flag specifies the values (e.g. columns) whose raw values will be compared
 based on the primary key join. The `--hash` flag will run a checksum across specified columns in
 the table. This will include casting to string, sanitizing the data (ifnull, rtrim, upper), concatenating,
 and finally hashing the row.
 
-
 Under the hood, row validation uses
 [Calculated Fields](https://github.com/GoogleCloudPlatform/professional-services-data-validator#calculated-fields) to
 apply functions such as IFNULL() or RTRIM(). These can be edited in the YAML or JSON config file to customize your row validation.
@@ -188,16 +187,17 @@ data-validation
                         Comma separated list of tables in the form schema.table=target_schema.target_table
                         Target schema name and table name are optional.
                         i.e 'bigquery-public-data.new_york_citibike.citibike_trips'
-  --primary-keys or -pk PRIMARY_KEYS
-                        Comma separated list of columns to use as primary keys.  See *Primary Keys* section
   --comparison-fields or -comp-fields FIELDS
                         Comma separated list of columns to compare. Can either be a physical column or an alias
                         See: *Calculated Fields* section for details
   --hash COLUMNS        Comma separated list of columns to hash or * for all columns
   --concat COLUMNS      Comma separated list of columns to concatenate or * for all columns (use if a common hash function is not available between databases)
+  [--primary-keys PRIMARY_KEYS, -pk PRIMARY_KEYS]
+                        Comma separated list of primary key columns, when not specified the value will be inferred
+                        from the source or target table if available.  See *Primary Keys* section
   [--exclude-columns or -ec]
                         Flag to indicate the list of columns provided should be excluded from hash or concat instead of included.
-  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE]
+  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE or CONNECTION_NAME.DATASET.TABLE]
                         BigQuery destination for validation results. Defaults to stdout.
                         See: *Validation Reports* section
   [--service-account or -sa PATH_TO_SA_KEY]
@@ -262,8 +262,6 @@ data-validation
                         Either --tables-list or --source-query (or file) and --target-query (or file) must be provided
   --target-query-file TARGET_QUERY_FILE, -tqf TARGET_QUERY_FILE
                         File containing the target sql command. Supports GCS and local paths.
-  --primary-keys PRIMARY_KEYS, -pk PRIMARY_KEYS
-                        Comma separated list of primary key columns 'col_a,col_b'.  See *Primary Keys* section
   --comparison-fields or -comp-fields FIELDS
                         Comma separated list of columns to compare. Can either be a physical column or an alias
                         See: *Calculated Fields* section for details
@@ -277,7 +275,10 @@ data-validation
   --partition-num INT, -pn INT
                         Number of partitions into which the table should be split, e.g. 1000 or 10000
                         In case this value exceeds the row count of the source/target table, it will be decreased to max(source_row_count, target_row_count)
-  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE]
+  [--primary-keys PRIMARY_KEYS, -pk PRIMARY_KEYS]
+                        Comma separated list of primary key columns, when not specified the value will be inferred
+                        from the source or target table if available.  See *Primary Keys* section
+  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE or CONNECTION_NAME.DATASET.TABLE]
                         BigQuery destination for validation results. Defaults to stdout.
                         See: *Validation Reports* section
   [--service-account or -sa PATH_TO_SA_KEY]
@@ -323,7 +324,7 @@ data-validation
                         Comma separated list of tables in the form schema.table=target_schema.target_table. Or shorthand schema.* for all tables.
                         Target schema name and table name are optional.
                         e.g.: 'bigquery-public-data.new_york_citibike.citibike_trips'
-  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE]
+  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE or CONNECTION_NAME.DATASET.TABLE]
                         BigQuery destination for validation results. Defaults to stdout.
                         See: *Validation Reports* section
   [--service-account or -sa PATH_TO_SA_KEY]
@@ -383,7 +384,7 @@ data-validation
   [--std COLUMNS]       Comma separated list of columns for stddev_samp or * for all numeric
   [--exclude-columns or -ec]
                         Flag to indicate the list of columns provided should be excluded and not included.
-  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE]
+  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE or CONNECTION_NAME.DATASET.TABLE]
                         BigQuery destination for validation results. Defaults to stdout.
                         See: *Validation Reports* section
   [--service-account or -sa PATH_TO_SA_KEY]
@@ -448,11 +449,11 @@ data-validation
   --hash '*'            '*' to hash all columns.
   --concat COLUMNS      Comma separated list of columns to concatenate or * for all columns
                         (use if a common hash function is not available between databases)
-  --primary-key or -pk JOIN_KEY
-                       Common column between source and target tables for join
+  [--primary-keys PRIMARY_KEYS, -pk PRIMARY_KEYS]
+                       Common column between source and target queries for join
   [--exclude-columns or -ec]
                         Flag to indicate the list of columns provided should be excluded from hash or concat instead of included.
-  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE]
+  [--bq-result-handler or -bqrh PROJECT_ID.DATASET.TABLE or CONNECTION_NAME.DATASET.TABLE]
                         BigQuery destination for validation results. Defaults to stdout.
                         See: *Validation Reports* section
   [--service-account or -sa PATH_TO_SA_KEY]
@@ -679,6 +680,8 @@ In many cases, validations (e.g. count, min, max etc) produce one row per table.
 and target table is to compare the value for each column in the source with the value of the column in the target.
 `grouped-columns` validation and `validate row` produce multiple rows per table. Data Validation Tool needs one or more columns to uniquely identify each row so the source and target can be compared. Data Validation Tool refers to these columns as primary keys. These do not need to be primary keys in the table. The only requirement is that the keys uniquely identify the row in the results.
 
+These columns are inferred, where possible, from the source/target table or can be provided via the `--primary-keys` flag.
+
 ### Grouped Columns
 
 Grouped Columns contain the fields you want your aggregations to be broken out

{google_pso_data_validator-6.3.0 → google_pso_data_validator-7.0.0}/data_validation/__main__.py

@@ -24,7 +24,10 @@ from data_validation import (
     cli_tools,
     clients,
     consts,
+    exceptions,
+    raw_query,
     state_manager,
+    util,
 )
 from data_validation.config_manager import ConfigManager
 from data_validation.data_validation import DataValidation
@@ -89,6 +92,7 @@ def get_aggregate_config(args, config_manager: ConfigManager):
         "!int64",
         "!decimal",
     ]
+    uuid_types = ["uuid", "!uuid"]
 
     if args.wildcard_include_string_len:
         supported_data_types.extend(["string", "!string"])
@@ -127,7 +131,7 @@ def get_aggregate_config(args, config_manager: ConfigManager):
             "min",
             col_args,
             args.exclude_columns,
-            supported_data_types,
+            supported_data_types + uuid_types,
             cast_to_bigint=cast_to_bigint,
         )
     if args.max:
@@ -136,7 +140,7 @@ def get_aggregate_config(args, config_manager: ConfigManager):
             "max",
             col_args,
             args.exclude_columns,
-            supported_data_types,
+            supported_data_types + uuid_types,
             cast_to_bigint=cast_to_bigint,
         )
     if args.bit_xor:
@@ -217,22 +221,20 @@ def _get_calculated_config(args, config_manager: ConfigManager) -> List[dict]:
     return calculated_configs
 
 
-def _get_comparison_config(args, config_manager: ConfigManager) -> List[dict]:
+def _get_comparison_config(
+    args, config_manager: ConfigManager, primary_keys: list
+) -> List[dict]:
     col_list = (
         None
-        if config_manager.comparison_fields == "*"
-        else cli_tools.get_arg_list(config_manager.comparison_fields)
+        if args.comparison_fields == "*"
+        else cli_tools.get_arg_list(args.comparison_fields)
     )
     comparison_fields = config_manager.build_comp_fields(
         col_list,
         args.exclude_columns,
     )
     # We can't have the PK columns in the comparison SQL twice therefore filter them out here if included.
-    comparison_fields = [
-        _
-        for _ in comparison_fields
-        if _ not in cli_tools.get_arg_list(args.primary_keys.casefold())
-    ]
+    comparison_fields = [_ for _ in comparison_fields if _ not in primary_keys]
 
     # As per #1190, add rstrip for Teradata string comparison fields
     if (
@@ -312,18 +314,25 @@ def build_config_from_args(args: Namespace, config_manager: ConfigManager):
             _get_calculated_config(args, config_manager)
         )
 
-        # Append Comparison fields
-        if args.comparison_fields:
-            config_manager.append_comparison_fields(
-                _get_comparison_config(args, config_manager)
-            )
-
         # Append primary_keys
         primary_keys = cli_tools.get_arg_list(args.primary_keys)
+        if not primary_keys and config_manager.validation_type != consts.CUSTOM_QUERY:
+            primary_keys = config_manager.auto_list_primary_keys()
+        if not primary_keys:
+            raise ValueError(
+                "No primary keys were provided and neither the source or target tables have primary keys. Please include --primary-keys argument"
+            )
+        primary_keys = [_.casefold() for _ in primary_keys]
         config_manager.append_primary_keys(
             config_manager.build_column_configs(primary_keys)
         )
 
+        # Append Comparison fields
+        if args.comparison_fields:
+            config_manager.append_comparison_fields(
+                _get_comparison_config(args, config_manager, primary_keys)
+            )
+
     return config_manager
 
 
@@ -331,22 +340,25 @@ def build_config_managers_from_args(
     args: Namespace, validate_cmd: str = None
 ) -> List[ConfigManager]:
     """Return a list of config managers ready to execute."""
-    configs = []
 
-    # Get pre build configs to build ConfigManager objects
-    pre_build_configs_list = cli_tools.get_pre_build_configs(args, validate_cmd)
+    def _build_configs():
+        configs = []
+
+        # Get pre build configs to build ConfigManager objects
+        pre_build_configs_list = cli_tools.get_pre_build_configs(args, validate_cmd)
 
-    # Build a list of ConfigManager objects
-    for pre_build_configs in pre_build_configs_list:
-        config_manager = ConfigManager.build_config_manager(**pre_build_configs)
+        # Build a list of ConfigManager objects
+        for pre_build_configs in pre_build_configs_list:
+            config_manager = ConfigManager.build_config_manager(**pre_build_configs)
 
-        # Append post build configs to ConfigManager object
-        config_manager = build_config_from_args(args, config_manager)
+            # Append post build configs to ConfigManager object
+            config_manager = build_config_from_args(args, config_manager)
 
-        # Append ConfigManager object to configs list
-        configs.append(config_manager)
+            # Append ConfigManager object to configs list
+            configs.append(config_manager)
+        return configs
 
-    return configs
+    return util.timed_call("Build config", _build_configs)
 
 
 def config_runner(args):
@@ -388,9 +400,26 @@ def config_runner(args):
                 )
             config_file_names = cli_tools.list_validations(config_dir=args.config_dir)
             config_managers = []
+            errors = False
             for file in config_file_names:
                 config_managers = build_config_managers_from_yaml(args, file)
-                run_validations(args, config_managers)
+                try:
+                    logging.info(
+                        "Currently running the validation for YAML file: %s",
+                        file,
+                    )
+                    run_validations(args, config_managers)
+                except Exception as e:
+                    errors = True
+                    logging.error(
+                        "Error '%s' occurred while running config file %s. Skipping it for now.",
+                        str(e),
+                        file,
+                    )
+            if errors:
+                raise exceptions.ValidationException(
+                    "Some of the validations raised an exception"
+                )
     else:
         if args.kube_completions:
             logging.warning(
@@ -429,20 +458,7 @@ def build_config_managers_from_yaml(args, config_file_path):
     return config_managers
 
 
-def run_raw_query_against_connection(args):
-    """Return results of raw query for ad hoc usage."""
-    mgr = state_manager.StateManager()
-    client = clients.get_data_client(mgr.get_connection_config(args.conn))
-    cursor = client.raw_sql(args.query)
-    res = cursor.fetchall()
-    try:
-        cursor.close()
-    except Exception:
-        pass
-    return res
-
-
-def convert_config_to_yaml(args, config_managers):
+def convert_config_to_yaml(args, config_managers: list):
     """Return dict objects formatted for yaml validations.
 
     Args:
@@ -462,7 +478,7 @@ def convert_config_to_yaml(args, config_managers):
     return yaml_config
 
 
-def convert_config_to_json(config_managers) -> dict:
+def convert_config_to_json(config_managers: list) -> dict:
     """Return dict objects formatted for json validations.
     JSON configs correspond to ConfigManager objects and therefore can only correspond to
     one table validation.
@@ -482,7 +498,7 @@ def convert_config_to_json(config_managers) -> dict:
     return json_config
 
 
-def run_validation(config_manager, dry_run=False, verbose=False):
+def run_validation(config_manager: ConfigManager, dry_run=False, verbose=False):
     """Run a single validation.
 
     Args:
@@ -490,11 +506,24 @@ def run_validation(config_manager, dry_run=False, verbose=False):
         dry_run (bool): Print source and target SQL to stdout in lieu of validation.
         verbose (bool): Validation setting to log queries run.
     """
+    # Only use cached connection for SQLAlchemy backends that manage reconnects for us.
+    source_client = (
+        config_manager.source_client
+        if clients.is_sqlalchemy_backend(config_manager.source_client)
+        else None
+    )
+    target_client = (
+        config_manager.target_client
+        if clients.is_sqlalchemy_backend(config_manager.target_client)
+        else None
+    )
     with DataValidation(
         config_manager.config,
         validation_builder=None,
         result_handler=None,
         verbose=verbose,
+        source_client=source_client,
+        target_client=target_client,
     ) as validator:
 
         if dry_run:
@@ -543,23 +572,7 @@ def run_validations(args, config_managers):
     """
     # TODO(issue/31): Add parallel execution logic
     for config_manager in config_managers:
-        if config_manager.config and consts.CONFIG_FILE in config_manager.config:
-            logging.info(
-                "Currently running the validation for YAML file: %s",
-                config_manager.config[consts.CONFIG_FILE],
-            )
-            try:
-                run_validation(
-                    config_manager, dry_run=args.dry_run, verbose=args.verbose
-                )
-            except Exception as e:
-                logging.error(
-                    "Error %s occurred while running config file %s. Skipping it for now.",
-                    str(e),
-                    config_manager.config[consts.CONFIG_FILE],
-                )
-        else:
-            run_validation(config_manager, dry_run=args.dry_run, verbose=args.verbose)
+        run_validation(config_manager, dry_run=args.dry_run, verbose=args.verbose)
 
 
 def store_yaml_config_file(args, config_managers):
@@ -674,7 +687,9 @@ def main():
     elif args.command == "find-tables":
         print(find_tables_using_string_matching(args))
     elif args.command == "query":
-        print(run_raw_query_against_connection(args))
+        raw_query.print_raw_query_output(
+            raw_query.run_raw_query_against_connection(args)
+        )
     elif args.command == "validate":
         validate(args)
     elif args.command == "generate-table-partitions":