> 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
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
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
On Thu, Apr 05, 2018 at 02:12:28AM -, john.calc...@gmail.com wrote:
> What is jclouds's general policy with regard to putting a blob to a cloud
> service where the blob already exists and the cloud provider doesn't allow
> overwrites?
>
> Seems like it would be nice to be able to treat the
What is jclouds's general policy with regard to putting a blob to a cloud
service where the blob already exists and the cloud provider doesn't allow
overwrites?
Seems like it would be nice to be able to treat the operation like it's an
idempotent http PUT, but if the service disallows
