Table of Contents

Search

  1. Preface
  2. Understanding Pipeline Partitioning
  3. Partition Points
  4. Partition Types
  5. Pushdown Optimization
  6. Pushdown Optimization Transformations
  7. Real-time Processing
  8. Commit Points
  9. Row Error Logging
  10. Workflow Recovery
  11. Stopping and Aborting
  12. Concurrent Workflows
  13. Grid Processing
  14. Load Balancer
  15. Workflow Variables
  16. Parameters and Variables in Sessions
  17. Parameter Files
  18. FastExport
  19. External Loading
  20. FTP
  21. Session Caches
  22. Incremental Aggregation
  23. Session Log Interface
  24. Understanding Buffer Memory
  25. High Precision Data
  26. POWERCENTERHELP

Advanced Workflow Guide

Advanced Workflow Guide

Pushdown Optimization for Key-Range Partitioning

Pushdown Optimization for Key-Range Partitioning

When you configure pushdown optimization for a session with key-range partitioning at the Source Qualifier transformation, the Integration Service merges all the rows into the first partition and passes empty data for each subsequent partition. The Integration Service creates an SQL statement for each partition. If the Integration Service pushes only part of the transformation logic to the database, it does not redistribute the rows across partitions when it runs the session.
The session must meet the following criteria to enable the Integration Service to push all transformation logic to the database:
  • The end key range for each partition must equal the start range for the next partition to merge all rows into the first partition. The end key range cannot overlap with the next partition. For example, if the end range for the first partition is 3386, then the start range for the second partition must be 3386.
  • You must configure the partition point at the Source Qualifier transformation to use key range partitioning and all subsequent partition points to use either hash auto-keys or pass-through partitioning.


Updated July 04, 2018