Skip to main content Skip to complementary content

Generating a regular expression from the Date Pattern Frequency indicator

You can generate a regular pattern from the results of an analysis that uses the Date Pattern Frequency indicator on a date column.

Before you begin

In the Profiling perspective of Talend Studio, a column analysis is created on a date column using the Date Pattern Frequency indicator.

Information noteNote: To be able to use the Date Pattern Frequency indicator on date columns, you must set the execution engine to Java in the Analysis Parameter view of the column analysis editor. For more information on execution engines, see Using the Java or the SQL engine.

For more information on how to create a column analysis, see Creating a basic analysis on a database column.

Procedure

  1. In the DQ Repository tree view, right-click the column analysis that uses the date indicator on a date column.
  2. Select Open from the contextual menu to open the corresponding analysis editor.
  3. Press F6 to execute the analysis and display the analysis results in the Analysis Results view of the editor.
    In this example, 100.00% of the date values follow the pattern yyyy MM dd and 39.41% follow the pattern yyyy dd MM.
  4. Right-click the date value for which you want to generate a regular expression and select Generate Regex Pattern from the contextual menu.
    The New Regex Pattern dialog box is displayed.
  5. Click Next.
    The date regular expression is already defined in the corresponding field.
  6. Click Finish to proceed to the next step.

    The pattern editor opens with the defined metadata and the generated pattern definition.

    The new regular expression is listed under Pattern > Regex in the DQ Repository tree view. You can drag it onto any date column in the analysis editor.
  7. Optional: Click the Test button to test a character sequence against this date regular expression as outlined in Testing a regular expression in the Pattern Test View.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here