Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Aggregator transformation
  6. Cleanse transformation
  7. Data Masking transformation
  8. Data Services transformation
  9. Deduplicate transformation
  10. Expression transformation
  11. Filter transformation
  12. Hierarchy Builder transformation
  13. Hierarchy Parser transformation
  14. Hierarchy Processor transformation
  15. Input transformation
  16. Java transformation
  17. Java transformation API reference
  18. Joiner transformation
  19. Labeler transformation
  20. Lookup transformation
  21. Machine Learning transformation
  22. Mapplet transformation
  23. Normalizer transformation
  24. Output transformation
  25. Parse transformation
  26. Python transformation
  27. Rank transformation
  28. Router transformation
  29. Rule Specification transformation
  30. Sequence Generator transformation
  31. Sorter transformation
  32. SQL transformation
  33. Structure Parser transformation
  34. Transaction Control transformation
  35. Union transformation
  36. Velocity transformation
  37. Verifier transformation
  38. Web Services transformation

Transformations

Transformations

Rules and guidelines for using a Structure Parser transformation

Rules and guidelines for using a Structure Parser transformation

Consider the following rules and guidelines when you use a Structure Parser transformation in a mapping:
  • When you select a mapping that contains a Structure Parser transformation in the Mapping Designer, and the associated
    intelligent structure model
    changed after it was associated with the transformation, a message appears in the Mapping Designer. Click the link that is provided in the message to update the model so that it complies with the mapping.
  • If you update an
    intelligent structure model
    that was created with an older version of
    Intelligent Structure Discovery
    , where all output fields were assigned a string data type, the Structure Parser transformation might change field data types during the update. If, for any of the affected fields, the downstream transformation or the target expects a string, edit the model to change the data type back to string. Then, in the Mapping Designer, click the provided link to update the model in the transformation again.
    For more information about editing an
    intelligent structure model
    , see
    Components
    .
  • Before you run a mapping with a Hadoop Files source, verify that you configured the field mapping correctly. The source fields and the Structure Parser transformation incoming fields have the same names, so you can automatically map the fields. For configuration information, see Processing input from a Hadoop Files source.
  • Before you run a mapping with a flat file source, verify that the Source transformation uses a reference file that contains a list of paths to the files that you want the Structure Parser transformation to process. When you configure the Source transformation, do not select the file that you want to process. Ensure that the Source transformation has one source field. Ensure that the Structure Parser transformation accesses the source field on the
    Field Mapping
    tab. For configuration information, see Processing input from a flat file source.
  • When you use a Structure Parser transformation in a mapplet, to prevent runtime errors, be sure that the combined Mapplet transformation name doesn't exceed 80 characters. For more information, see Mapplet transformation names.

0 COMMENTS

We’d like to hear from you!