×

Validating code of an extract, transform and load (ETL) tool

  • US 9,244,809 B1
  • Filed: 07/15/2014
  • Issued: 01/26/2016
  • Est. Priority Date: 07/15/2014
  • Status: Expired due to Fees
First Claim
Patent Images

1. A method of validating code of an extract, transform and load (ETL) tool, the method comprising the steps of:

  • responsive to a receipt of naming, coding, and performance standards for the code of the ETL tool and an export of the code of the ETL tool to a job definition file, a computer parsing the code of the ETL tool in the job definition file;

    the computer determining violations of the naming, coding, and performance standards in part by determining the parsed code of the ETL tool does not match the naming, coding, and performance standards;

    the computer generating a report which identifies the violations;

    based at least in part on a review of the report and a rework of the code of the ETL tool to comply with the naming, coding and performance standards and responsive to an export of the reworked code of the ETL tool to another job definition file, the computer parsing the reworked code of the ETL tool in the other job definition file, determining that the parsed reworked code of the ETL tool does not include the violations of the naming, coding and performance standards, and generating a second report that indicates that the reworked code of the ETL tool does not include the violations;

    the computer determining whether the code of the ETL tool specifies an automatic selection of a partitioning method for a link in the code of the ETL tool;

    the computer determining whether first parameter(s) are present in the code of the ETL tool as parameter(s) of a job included in the code of the ETL tool;

    the computer determining whether second parameter(s) are not present in the code of the ETL tool as parameter(s) of the job;

    the computer determining whether the job is annotated in a description field;

    the computer determining whether the description field of the job includes a value specified by a job annotation standard included in the naming, coding, and performance standards;

    the computer determining whether the description field includes a name of the job;

    the computer determining whether a job activity in a sequence having a parameter passes a value specified by a job activity parameter standard included in the naming, coding, and performance standards;

    the computer determining whether an add checkpoints feature is enabled for the sequence so that jobs in the sequence are restartable on failure of the jobs;

    the computer determining whether a handle activities that fail feature is enabled for the sequence so that an activity of a failing job in the sequence is handled by triggering automatically inserted code that branches to an error handling point;

    the computer determining whether a log job errors feature is enabled for the sequence so that a message is logged about a job whose run ends with a warning or fatal error;

    the computer determining whether a log job reports feature is enabled for the sequence so that a status report is logged after a run of the job whose run ends with the warning or fatal error;

    the computer determining whether a reset if required and then run feature is enabled for the sequence so that the job is run each time the sequence is run, even after a run of the sequence is aborted;

    the computer determining whether a surrogate key is generated in a transformer stage; and

    based on the code of the ETL tool specifying the automatic selection of the partitioning method for the link in the code of the ETL tool, the first parameter(s) being present in the code of the ETL tool as the parameter(s) of the job, the second parameter(s) not being present in the code of the ETL tool as the parameter(s) of the job, the job not being annotated in the description field, the description field of the job not including the value specified by the job annotation standard, the description field not including the name of the job, the job activity does not pass the value specified by the job activity parameter standard, the add checkpoints feature not being enabled for the sequence, the handle activities that fail feature not being enabled for the sequence, the log job errors feature not being enabled for the sequence, the log job reports feature not being enabled for the sequence, the reset if required and then run feature not being enabled for the sequence, or the surrogate key is generated in the transformer stage, the computer determining a violation of the naming, coding, and performance standards.

View all claims
  • 2 Assignments
Timeline View
Assignment View
    ×
    ×