Does a tMap in a joblet have separate variables for each instance of the joblet?
I have a joblet with a tMap in it, and within that tMap I have a variable that I am using as a row counter. It appears that this variable maintains its value across all the instances of the joblet in my job! I would like each joblet to have its own row counter, is there a way to do that?
I suppose I could use a Numeric.sequence object, I can find a string that distinguishes between the different instances.
Does anyone know if Numeric.sequence is thread safe?
Can you post a screenshot of how you have your joblet used in a job? Unless something has changed that I am not aware of, a variable in a tMap within a Joblet should not be shared across each usage of that Joblet in a Job. Could you also show/describe how you have configured your counter variable?
It's possible that I was making some other mistake that created the appearance of this problem. I've made substantial changes to the job now anyway, I might find the time to create a test job to check this behaviour.
