Opened at 2011-09-02T00:32:21Z
Last modified at 2012-03-29T19:38:42Z
#1522 new defect
our use of the term "bucket" is ambiguous
Reported by: | davidsarah | Owned by: | somebody |
---|---|---|---|
Priority: | normal | Milestone: | undecided |
Component: | documentation | Version: | 1.9.0a1 |
Keywords: | terminology docs cruft | Cc: | |
Launchpad Bug: |
Description
We use "bucket" inconsistently to refer to either the collection of shares on a storage server with a given storage index, or the container for a single share.
When we add the S3 backend, there will also be a collision with S3's use of "bucket", meaning a collection of objects that has its own key namespace and is subject to a given access control and geographical region policy. That will probably will not correspond to a bucket in either of our senses.
Change History (2)
comment:1 Changed at 2011-10-06T19:03:10Z by davidsarah
- Keywords cruft added
comment:2 Changed at 2012-03-29T19:38:42Z by davidsarah
- Priority changed from major to normal
Note: See
TracTickets for help on using
tickets.