Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Big Data Management
  3. Connections
  4. Mappings in the Hadoop Environment
  5. Mapping Objects in the Hadoop Environment
  6. Processing Hierarchical Data on the Spark Engine
  7. Stateful Computing on the Spark Engine
  8. Monitoring Mappings in the Hadoop Environment
  9. Mappings in the Native Environment
  10. Profiles
  11. Native Environment Optimization
  12. Data Type Reference
  13. Complex File Data Object Properties
  14. Function Reference
  15. Parameter Reference

Rules and Guidelines for Complex Data Type Definitions

Rules and Guidelines for Complex Data Type Definitions

Consider the following rules and guidelines when you work with complex data type definitions:
  • A struct port or a struct element in a complex port must reference a complex data type definition.
  • You cannot reference a complex data type definition in one mapping to a complex port in another mapping.
  • You cannot reference a recursive data type definition to a struct port or a struct element in a complex port.
  • Changes to the elements in a complex data type definition are automatically propagated to complex ports that reference the complex data type definition.
  • If you change the name of the type definition library or the complex data type definition, you must update the name in expressions that use complex functions such as STRUCT_AS, RESPEC, and CAST.


Updated December 13, 2018