[jclouds-labs-google] Configure GCS consistency model as "STRICT" (#121)

[snotling <no...@github.com>]

AFAIK Google Cloud Storage provides a strong/strict consistency model.
https://cloud.google.com/storage/docs/concepts-techniques#consistency
You can merge this Pull Request by running:

  git pull https://github.com/snotling/jclouds-labs-google patch-1

Or you can view, comment on it, or merge it online at:

  https://github.com/jclouds/jclouds-labs-google/pull/121

-- Commit Summary --

  * Configure GCS consistency model as "STRICT"

-- File Changes --

    M google-cloud-storage/src/main/java/org/jclouds/googlecloudstorage/blobstore/config/GoogleCloudStorageBlobStoreContextModule.java (2)

-- Patch Links --

https://github.com/jclouds/jclouds-labs-google/pull/121.patch
https://github.com/jclouds/jclouds-labs-google/pull/121.diff

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/121

Re: [jclouds-labs-google] Configure GCS consistency model as "STRICT" (#121)

[snotling <no...@github.com>]

Indeed, I wasn't aware of the "peculiarity" regarding list operations in GCS.
And your consistency test report is very interesting as well.
But I'm afraid I won't be of any help on this topic, I'm simply a jclouds user which happened to browse through the source code :)
So I think my kind of PR can be closed, as it *is* appropriate to define the GCS as eventually consistent in jclouds for the moment.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/121#issuecomment-69893773

Re: [jclouds-labs-google] Configure GCS consistency model as "STRICT" (#121)

[Andrew Gaul <no...@github.com>]

Closed #121.

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/121#event-224143476

Re: [jclouds-labs-google] Configure GCS consistency model as "STRICT" (#121)

[Andrew Gaul <no...@github.com>]

@snotling List operations still have eventual consistency:

> List operations are eventually consistent. This eventual consistency applies to operations that get a <list> of objects or buckets. For example, if you upload an object to a bucket, you can immediately download that object and get its ACLs because object uploads are strongly consistent. However, if you upload an object to a bucket, and then immediately perform a list objects operation on the bucket in which the object is stored, the uploaded object might not immediately appear in the returned list of objects. This is also true if you create a bucket and then immediately perform a list buckets operation. The newly-created bucket will be immediately available for use, but the bucket might not immediately appear in the returned list of buckets.

We mostly use this attribute for tests to clear containers, for which we need to know if list is strongly consistent.  jclouds could break the consistency model out into various operations in a more granular way; would you like to look into this?  Here is another reference with cross-provider consistency results:

https://github.com/andrewgaul/are-we-consistent-yet#observed-consistency

---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-google/pull/121#issuecomment-69632353