Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Review your record counts. Before you specify the join, you should review your record counts and the uniqueness of your keys, which should provide an idea of the number of records you may see in the output. Note that the number of output records depends on the type of join and the matches between join keys.
  • Review your join key values. If there are variations in the values in your join keys, you may end up with duplicate records in your joined dataset. Look for mismatched or missing values in your join keys, and correct if possible.
  • Review the granularity of your data. If you bring together data at a lower fidelity than the source, you can end up with record matches that are not actually matching data. For example, if your timestamps are down-sampled from milliseconds to seconds as part of the join, you may have "matching" timestamps in seconds that were not matches at the millisecond level in the source data.

 

Step 1 - Select Dataset

In the Search panel, enter join.

...

OptionDescription
Use metaphone

Use the metaphone algorithm for key value matching with the strong matching requirement. Both primary encodings of each key value must match.

Tip

Tip: Use this option to perform fuzzy join matching of primary keys between datasets.

See DOUBLEMETAPHONEEQUALS Function.

Ignore caseIgnore case differences between the join key values for matching purposes.
Ignore special charactersIgnore all characters that are not alphanumeric, accented Latin characters, or whitespace, prior to testing for a match.
Ignore whitespaceIgnore all whitespace characters, including spaces, tabs, carriage returns, and newlines.

...

To add the specified join to your recipe, click Add to Recipe.