When I broke up the input data into a larger number of smaller files,
the "blob already exists" exceptions went away. Thanks for pointing
out this quirk with dev storage.
I'm going to try running my test scenario with a larger amount of data
in my real Azure environment tomorrow. I'm really eager to tinker with
the instance count and thread count settings and see how the system
responds.
I appreciate all your help!
-Mike
On Jun 9, 5:06 pm, Thilina Gunarathne <
cset...@gmail.com> wrote:
> That's bit strange. Before sending the fix your way, I was able to
> test successfully with multiple input files. In fact, I did it even now in
> my local development fabric. I'm using the Azure SDK 1.4.1 (April 2011). The
> strange thing is that, even when I use the same output container (the
> intermediate container name is derived from the out container name) for
> multiple jobs, the blobs get overridden without any complains.
>
> Are you using a large input with the local development storage? I have read
> in some forums(eg: [1]) that the dev storage throws this
> error intermittently for large files.
>
> thanks,
> Thilina
>
> [1]
http://social.msdn.microsoft.com/Forums/hu-HU/windowsazuredata/thread...