[
https://issues.apache.org/jira/browse/JCLOUDS-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Kistner updated JCLOUDS-1539:
----------------------------------
Description:
Since 2.1.0, the BlobBuilder includes a Tier field that always defaults to
Tier.STANDARD. This prevents newly created Blobs from inheriting the storage
class of the bucket itself.
In my case, I am using GCS and created a bucket with a default storage class of
NEARLINE:
{{$ gsutil mb -c NEARLINE gs://demo-bucket-nearline}}
{{$ gsutil defstorageclass get gs://demo-bucket-nearline}}
{{gs://demo-bucket-nearline: NEARLINE}}
{{$ touch .demo-gsutil && gsutil cp .demo-gsutil gs://demo-bucket-nearline$
gsutil stat gs://demo-bucket-nearline/.demo-gsutil}}
Storage class: NEARLINE
In previous versions of jclouds the BlobBuilder did not specify an overriding
storage class. I have attached a sample java application that uses jclouds
2.2.0 to show how this affects the storage class of newly created blobs:
{{$ gsutil stat gs://demo-bucket-nearline/.demo-1}}
Storage class: STANDARD
{{$ gsutil stat gs://demo-bucket-nearline/.demo-2}}
Storage class: NEARLINE
The issue can be worked around by specifying the tier on the BlobBuilder, but
that is only possible when the storage class on the bucket has a mapping in
jclouds.
was:
Since 2.1.0, the BlobBuilder includes a Tier field that always defaults to
Tier.STANDARD. This prevents newly created Blobs from inheriting the storage
class of the bucket itself.
In my case, I am using GCS and created a bucket with a default storage class of
NEARLINE:
{{$ gsutil mb -c NEARLINE gs://demo-bucket-nearline}}
{{$ gsutil defstorageclass get gs://demo-bucket-nearline}}
{{gs://demo-bucket-nearline: NEARLINE}}
{{$ touch .demo-gsutil && gsutil cp .demo-gsutil gs://demo-bucket-nearline$
gsutil stat gs://demo-bucket-nearline/.demo-gsutil}}
Storage class: NEARLINE
In previous versions of jclouds the BlobBuilder did not specify an overriding
storage class. I have attached a sample java application that uses jclouds
2.2.0 to show how this affects the storage class of newly created blobs:
{{$ gsutil stat gs://demo-bucket-nearline/.demo-1}}
Storage class: STANDARD
{{$ gsutil stat gs://demo-bucket-nearline/.demo-2}}
Storage class: NEARLINE
{{The issue can be worked around by specifying the tier on the BlobBuilder, but
that is only possible when the storage class on the bucket has a mapping in
jclouds.}}
> BlobBuilder always overrides default StorageClass Tier
> ------------------------------------------------------
>
> Key: JCLOUDS-1539
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1539
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-blobstore
> Affects Versions: 2.1.0, 2.2.0, 2.1.1, 2.1.2, 2.1.3
> Reporter: Ryan Kistner
> Priority: Minor
> Attachments: sample.java
>
>
> Since 2.1.0, the BlobBuilder includes a Tier field that always defaults to
> Tier.STANDARD. This prevents newly created Blobs from inheriting the storage
> class of the bucket itself.
>
> In my case, I am using GCS and created a bucket with a default storage class
> of NEARLINE:
> {{$ gsutil mb -c NEARLINE gs://demo-bucket-nearline}}
> {{$ gsutil defstorageclass get gs://demo-bucket-nearline}}
> {{gs://demo-bucket-nearline: NEARLINE}}
> {{$ touch .demo-gsutil && gsutil cp .demo-gsutil gs://demo-bucket-nearline$
> gsutil stat gs://demo-bucket-nearline/.demo-gsutil}}
> Storage class: NEARLINE
>
> In previous versions of jclouds the BlobBuilder did not specify an overriding
> storage class. I have attached a sample java application that uses jclouds
> 2.2.0 to show how this affects the storage class of newly created blobs:
>
> {{$ gsutil stat gs://demo-bucket-nearline/.demo-1}}
> Storage class: STANDARD
> {{$ gsutil stat gs://demo-bucket-nearline/.demo-2}}
> Storage class: NEARLINE
>
> The issue can be worked around by specifying the tier on the BlobBuilder, but
> that is only possible when the storage class on the bucket has a mapping in
> jclouds.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
