I have retrieved data from database in sequential execution mode, I sorted the data in sequential execution mode , I pushed the data through a Transformer in sequential execution mode. In the transformer I added a new column ( XYZ ) , In the next step I am trying to create a dataset using XYZ as the key for HASH Partitioning.
I have built all these steps in one job. The partitioning with XYZ is not working. But at the same step, if I use one of the columns that was retrieved from the database as the key for Hash partitioning. It is partitioning fine. Does it mean we should not be using intermediate values as key for partitioning?
Hash Partitioning Question
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
This question is something like I need to go some where, on a cross road if I take one road i reach my destination and if not, i don't reach there. What is the problem? The problem is you did not read the sign board. Simple mistake but can cause trouble if you are short on gas, cash and time
Are you passing a constant value to that column?
Are you passing a constant value to that column?
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.
Genius may have its limitations, but stupidity is not thus handicapped.
DataStage has no general problem with using a column created in a transform stage as the hash partitioning key downstream. Could you explain what the column type and contents are and what the partitioning did differently from what you expected?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>