Thanks for your reply
chulett wrote:Sorry, it's been awhile but can't you sort and create the key change column at the same time? Meaning two rather than three Sort stages.
Yes, Sort does create a keyChange while sorting, but i don't want the keyChange with 5 keys (A,B,C,D,E) but with rather one keyChange with (A,B,C) keys and another with just A as key.
Code: Select all
Say for example A = COUNTRY, B = STATE, C = ORDER, D = PRODUCTS E = xxxx
I need to sort on all these keys to process the data and then i would need a key change till ORDER and another key change just for the COUNTRY to route and process them differently.
I don't think you need to be too concerned about the performance impact of "Don't Sort" stages but curious what others think. And 3M isn't really a large amount to sort IMHO unless your infrastructure is not up to the task.
Our infrastructure is well built, and I could still ask for more cpu if need be. But would really like my design to be well made to put forth my points and demand them.
I would go ahead and implement with 3 sort stage with 2 of them needing just for keyChange.
And definetly as said, it would be great to have others views as well .
Thanks
Sen