Re: putBlob with an already existing object

2018-04-05 Thread john . calcote
> multi-part uploads. Unfortunately Atmos is odd for a number of reasons > and delete and retry was the best workaround at the time, especially for > a low-popularity provider. Some blobstores like Ceph can address this > issue with conditional PUT but this is not supported elsewhere. In the

Re: putBlob with an already existing object

2018-04-05 Thread Andrew Gaul
On Thu, Apr 05, 2018 at 04:03:04PM -, john.calc...@gmail.com wrote: > Thanks for the quick response Andrew - > > > The closet analog is AtmosUtils.putBlob which retries on > > KeyAlreadyExistsException after removing. Generally the jclouds > > portable abstraction tries to make all

Re: putBlob with an already existing object

2018-04-05 Thread john . calcote
Thanks for the quick response Andrew - > The closet analog is AtmosUtils.putBlob which retries on > KeyAlreadyExistsException after removing. Generally the jclouds > portable abstraction tries to make all blobstores act the same and uses > the native behavior for the providers. Which blobstore