Skip to main content Skip to complementary content
Announcements

Importing a parser rule

You can import one parser rule at a time.

Before you begin

The parser rule must be in CSV format. The CSV file must have specific columns including the ones listed in the table below. The CSV file may contain only a few of them.
Column name Description Required/Optional
Label Name of the rule set Required
Purpose Purpose of the rule set Optional
Description Descriptive information of the rule set Optional
Author Author of the rule set Optional
Relative Path Path to the folder storing the rule set. This path is relative to the root. Optional
Name Name of the rule in the rule set Required
Type Type of the rule Required
Value Value of the rule Required

Procedure

  1. In the DQ Repository tree view of the Profiling perspective, expand Libraries > Rules.
  2. Right-click Parser and click Import Parser Rule.
    Contextual menu of the Parser folder.
    The Import Parser Rule wizard opens.
  3. Browse to the folder containing the parser rule you want to import and select the file to import.
    A preview of the file is displayed in the Preview area.
  4. In the Duplicate ParserRule handling area, select:
    Option To...
    skip existing ParserRule

    import the parser rule only if it does not already exist. A warning message is displayed if the imported parser rule already exists under the Parser folder.
    rename new ParserRule with suffix
    rename the imported parser rule with a suffix. This option prevents from overwriting an existing parser rule. Talend Studio detects that the parser rule being imported is identical to an existing one. The detection is based on the configuration, not the name, of the parser rule. The imported parser rule is renamed from the existing one.
    Example of a new parser rule renamed from an existing one.
  5. Click Finish.
    The parser rule is imported under the Parser folder.

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 – let us know how we can improve!

Leave your feedback here