Yes if the location is made sure to exist before this is written.
I am pretty sure you wont have to insert 100s of locations every load. It is a one time thing.
Glad you figured it!!
Thanks, that approach makes more sense now.
As far as locking goes there isn’t anything in the product that would function like you were thinking at this point.
What Naveen mentioned is right. Is there any way to possibly preprocess the data so that you’d only have one instance of a place across your incoming documents (could be dangerous, if the one with the data fails)?
I’m not sure how your SOAP endpoint functions, are you just publishing flat employee records in one soap call or are you making multiple soap calls per incoming document to write pieces of the employee record to different places?
Is there any danger from your side having the duplicate data overwrite for your application?
Thanks, in our case, we have to make multiple soap calls per incoming document. There’s no other choice to do that.
But anyway. I somehow organize the data a little bit, removed the duplicate location from the data.
Now I am able to leverage the pool size of Pipeline Execute without worrying about the race condition.
Thanks again
Yes if the location is made sure to exist before this is written.
I am pretty sure you wont have to insert 100s of locations every load. It is a one time thing.
Glad you figured it!!
