Table of Contents

Search

  1. Preface
  2. Introduction to Transformations
  3. Transformation Ports
  4. Transformation Caches
  5. Address Validator Transformation
  6. Aggregator Transformation
  7. Association Transformation
  8. Bad Record Exception Transformation
  9. Case Converter Transformation
  10. Classifier Transformation
  11. Comparison Transformation
  12. Consolidation Transformation
  13. Data Masking Transformation
  14. Data Processor Transformation
  15. Decision Transformation
  16. Duplicate Record Exception Transformation
  17. Expression Transformation
  18. Filter Transformation
  19. Hierarchical to Relational Transformation
  20. Java Transformation
  21. Java Transformation API Reference
  22. Java Expressions
  23. Joiner Transformation
  24. Key Generator Transformation
  25. Labeler Transformation
  26. Lookup Transformation
  27. Lookup Caches
  28. Dynamic Lookup Cache
  29. Match Transformation
  30. Match Transformations in Field Analysis
  31. Match Transformations in Identity Analysis
  32. Normalizer Transformation
  33. Merge Transformation
  34. Parser Transformation
  35. Python Transformation
  36. Rank Transformation
  37. Read Transformation
  38. Relational to Hierarchical Transformation
  39. REST Web Service Consumer Transformation
  40. Router Transformation
  41. Sequence Generator Transformation
  42. Sorter Transformation
  43. SQL Transformation
  44. Standardizer Transformation
  45. Union Transformation
  46. Update Strategy Transformation
  47. Web Service Consumer Transformation
  48. Parsing Web Service SOAP Messages
  49. Generating Web Service SOAP Messages
  50. Weighted Average Transformation
  51. Window Transformation
  52. Write Transformation
  53. Appendix A: Transformation Delimiters

Developer Transformation Guide

Developer Transformation Guide

Creating a Write Transformation from an Existing Transformation

Creating a Write Transformation from an Existing Transformation

You can create a Write transformation with the same ports in a transformation that exists in the mapping.
You can create a target for complex files, flat files, or relational resources. If one of the ports in the existing transformation contains a complex port, you must create a complex file target and link ports by name or link ports at run time based on the link policy. The Developer tool can create an Avro, Parquet, ORC, or JSON complex file target.
  1. Open a mapping in the editor.
  2. Right-click a transformation in the mapping editor and select
    Create Target
    .
    The
    Create Target
    window opens.
  3. Choose a complex file, flat file, or relational data object type.
  4. Choose a link type.
    You can choose from the following link types:
    Link ports by name
    Ports in the Write transformation correspond to those in the source and have the same names.
    Link dynamic port based on the mapping flow
    The Write transformation contains dynamic ports based on upstream objects in the mapping flow.
    Link ports at run time based on link policy
    Ports are created in the target at run time based on the link policy that you configure on the Run Time Linking tab of the Write transformation.
    For more information about dynamic ports and run-time link configuration, see the
    Informatica Developer Mapping Guide.
  5. Name the new data object.
  6. Optionally, click
    Browse
    to select a location for the data object.
  7. If you chose to create a complex file target, select the complex file format as Avro or Parquet in the
    Resource Format
    drop-down box.
  8. Click
    Finish
    .
The Developer tool performs the following tasks:
  • Adds a Write transformation to the mapping.
    The following image shows a Write transformation created from a Read transformation:
    The Write transformation has the same columns as the Read transformation from which it was created.
  • Links ports.
  • Creates a physical data object.
    You can configure the physical data object properties. For example, you must specify an HDFS connection for the complex file data object.

0 COMMENTS

We’d like to hear from you!