I am trying to see if there is a way we can implement NOT IN logic in FILTER stage. I can use the 2nd method of doing it in the transformer but wondering what's wrong with the 1st one. Does filter stage not support NOT IN ? I understand that all the conditions won't be true for one record and thats why I gave OR so it works across multiple records.
Parallel Job Developer's Guide wrote:The following list summarizes the Boolean expressions that are supported. In the list, BOOLEAN denotes
any Boolean expression.
- true
- false
- six comparison operators: =, <>, <, >, <=, >=
- is null
- is not null
- like 'abc' (the second operand must be a regular expression)
- between (for example, A between B and C is equivalent to B <= A and A> = C)
- not BOOLEAN
- BOOLEAN is true
- BOOLEAN is false
- BOOLEAN is not true
- BOOLEAN is not false
Any of these can be combined using AND or OR.
No IN and no NOT IN.
You might contemplate using a Data Rules stage if you're running version 8.7 and have Information Analyzer licensed. It does support IN, NOT IN, MATCHES regular_expression and lots of others.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
AND works but the problem is if there are Null values in the field being cheked then we have to explicitly specify that where as in SQL it takes care of it implicitly.
Thanks to all...
Last edited by kaps on Fri Jul 27, 2012 8:20 am, edited 1 time in total.