Datastage | Preserve Partitioning Flag

A stage can request that the next stage in the job preserves whatever partitioning it has implemented. It does this by setting the preserve partitioning flag for its output link. Note, however, that the next stage may ignore this request.

In most cases you are best leaving the preserve partitioning flag in its default state. The exception to this is where preserving existing partitioning is important.

The flag will not prevent repartitioning, but it will warn you that it has happened when you run the job.

If the Preserve Partitioning flag is cleared, this means that the current stage doesn’t care what the next stage in the job does about partitioning. 

On some stages, the Preserve Partitioning flag can be set to Propagate. In this case the stage sets the flag on its output link according to what the previous stage in the job has set. 

If the previous job is also set to Propagate, the setting from the stage before is used and so on until a Set or Clear flag is encountered earlier in the job. 

If the stage has multiple inputs and has a flag set to Propagate, its Preserve Partitioning flag is set if it is set on any of the inputs, or cleared if all the inputs are clear.

Post a Comment

Previous Post Next Post

Contact Form