Hello Forum,
It seems like the ability to provide a constant value for one of the key columns in a lookup is not possible in PX, as it was in server jobs. It looks as though you are forced to only use input columns in the key expressions.
Is this true?
Thanks,
Greg
Editing Key Expressions
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Then, yes, it's true within the Lookup stage. But you could, of course, precede the Lookup stage with a Column Generator stage that uses a cycle from N to N for the column in question (one way to generate a constant).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Thank you for your response.
Currently, I precede with transformer that appends the constants to my other primary link fields. Your solution sounds more complicated. Is is faster than using a transformer?ray.wurlod wrote:Then, yes, it's true within the Lookup stage. But you could, of course, precede the Lookup stage with a Column Generator stage that uses a cycle from N to N for the column in question (one way to generate a constant).
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
Column Generator will definitely be better then a Transformer unless you are using that Transformer for a range of other tasks (such as constraints and derivations) and it is more convenient to leave it in. The stage is not that complicated to use.
Better yet if your lookup source is a database put your constant into the database stage as a where clause using the parameter # values. This will reduce the number of rows your lookup stage needs to prepare.
If your source is not a database but is a dataset or sequential file you could send it to a filter stage using the constant to filter the lookup data, this will reduce the amount of memory your lookup stage uses and speed up the lookups with a small overhead on startup.
Better yet if your lookup source is a database put your constant into the database stage as a where clause using the parameter # values. This will reduce the number of rows your lookup stage needs to prepare.
If your source is not a database but is a dataset or sequential file you could send it to a filter stage using the constant to filter the lookup data, this will reduce the amount of memory your lookup stage uses and speed up the lookups with a small overhead on startup.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn