Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Data Engineering Integration
  3. Mappings
  4. Mapping Optimization
  5. Sources
  6. Targets
  7. Transformations
  8. Python Transformation
  9. Data Preview
  10. Cluster Workflows
  11. Profiles
  12. Monitoring
  13. Hierarchical Data Processing
  14. Hierarchical Data Processing Configuration
  15. Hierarchical Data Processing with Schema Changes
  16. Intelligent Structure Models
  17. Blockchain
  18. Stateful Computing
  19. Appendix A: Connections Reference
  20. Appendix B: Data Type Reference
  21. Appendix C: Function Reference

Rules and Guidelines for Midstream Parsing

Rules and Guidelines for Midstream Parsing

Consider the following rules and guidelines when you work with midstream parsing:
  • For optimal performance, the size of hierarchical data to be parsed should be 5 MB or less.
  • If the defined schema does not match the data, the parser ignores the unrecognized field and does not fail the mapping job.
  • Dynamic complex ports are not supported with midstream mapping.
  • Intelligent Structure Discovery
    converts Boolean data to a string in the intelligent structure model. Use a string field in the midstream mapping for any Boolean data.
  • The midstream mapping complex functions cannot parse Avro binary boolean data types.


Updated September 28, 2020