![Confused :?](./images/smilies/icon_confused.gif)
Many records written to a hashed file, all six fields are key fields. I don't think this matters, but for the record this is a pathed hash with a VOC record created for it, more on that later. Here are the four records we're interested in today, nothing changed to protect the innocent:
600000401502,1,DEP,600000587101,1,EMAILM
600000401502,1,DEP,600000587102,1,XLINE
600000401502,1,DEP,600000587099,1,WEBLINK
600000401502,1,DEP,600000587100,1,BDESC
When I do a 'View Data' of the hashed file and 'Find' for the value in the first field, what comes up in the viewer during the first pass are these four records:
600000401502,1,DEP,600000587101,1,EMAILM
600000401502,1,DEP,600000587102,1,XLINE
600000401502,1,DEP,600000587099,1,WEBLINK
600000401502,1,DEP,600000587102,1,XLINE
Note that record 2 is repeated in place of record 4. Click 'Find' one more time, it tells me it found nothing more and would I like to start over from the beginning, I say yes and it then shows me the correct four records:
600000401502,1,DEP,600000587101,1,EMAILM
600000401502,1,DEP,600000587102,1,XLINE
600000401502,1,DEP,600000587099,1,WEBLINK
600000401502,1,DEP,600000587100,1,BDESC
Why in the Blue Blazes does the first pass thru the hashed file return bad data? Every subsequent pass thru it shows correctly until I close and reopen the viewer, at which point the behaviour repeats itself. This problem is also manifesting itself in the job that leverages this hashed file (via a UV stage with a single key field marked so it returns multiple records) the BDESC record is not being returned, but rather the XLINE one is coming down twice instead. Also note this View Data behaviour is consistent regardless of if we check via the hashed file stage or via the UV stage, both exhibit the same troublesome behaviour.
I've run UVFIXFILE on the hashed file and it showed no issues. Any ideas? Things to try? I'm... baffled.