IN CONSTRAINS I GIVINING THIS CONDITION
Feed.HFEDU_ID <> LKPHash.HFEDU_ID
FOR NEW DATA LOAD AND FOR OTHER REJECT ROW
BUT FOR NOT EQUAL, I DON'T KNOW WHY THIS CONDITION IS NOT WORKING EVEN WHEN I AM GIVING Feed.HFEDU_ID = LKPHash.HFEDU_ID FOR REJECT ROW OR CAN SAY REJECT OLD ROW I AM GETTING PROPER RESULT,BUT IN LOG I M GETTING LOTS OF WARNING MESSAGES
can any one suggest me how we can use <> condition so i won't get any warnings in my log.
HOW TO GIVE NOT EQUAL CONDITION IN LOOKUP
Moderators: chulett, rschirm, roy
Please tell us what the warning messages are.
(and YOU DON'T NEED TO SHOUT, we may be old geezers but can still hear well enough when the batteries are charged )
(and YOU DON'T NEED TO SHOUT, we may be old geezers but can still hear well enough when the batteries are charged )
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Only "=" works with the Hashed File stage.
To use "<>", "BETWEEN" or any other operator you need an SQL-based stage serving the reference link. A UV stage would do it, or any database stage.
But first ask yourself is this really what you want? It will return very many rows for every row processed on your main (stream) input link.
To use "<>", "BETWEEN" or any other operator you need an SQL-based stage serving the reference link. A UV stage would do it, or any database stage.
But first ask yourself is this really what you want? It will return very many rows for every row processed on your main (stream) input link.
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.
As noted, only equal comparisons work in a Hash lookup. You check for 'not equal' by looking for the failure of your equal check. Typically. There will be an Output Link boolean variable called NOTFOUND that will be TRUE or you can check to see if your key value is null after the lookup - hash misses set all field values to null.
And as also noted, sharing whatever error messages you are getting helps us figure out what is going on.
And as also noted, sharing whatever error messages you are getting helps us figure out what is going on.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers