distribution/registry/storage/driver
Terin Stock b23dd1ef37 swift: correct segment path generation
When uploading segments to Swift, the registry generates a random file,
by taking the hash of the container path and 32-bytes of random data.
The registry attempts to shard across multiple directory paths, by
taking the first three hex characters as leader.

The implementation in registry, unfortunately, takes the hash of
nothing, and appends it to the path and random data. This results in all
segments being created in one directory.

Fixes: #2407
Fixes: #2311
Signed-off-by: Terin Stock <terinjokes@gmail.com>
2019-06-22 23:44:43 -07:00
..
azure Fix gometalint errors 2019-02-04 16:01:04 -08:00
base Add regulator to GCS 2018-09-05 15:48:30 -07:00
factory Add documentation for how to register new StorageDrivers 2016-03-29 14:42:19 -07:00
filesystem Add regulator to GCS 2018-09-05 15:48:30 -07:00
gcs Add back include_gcs build constraint 2018-09-05 15:48:30 -07:00
inmemory Fix gometalint errors 2019-02-04 16:01:04 -08:00
middleware Merge pull request #2849 from Shawnpku/master 2019-04-16 18:43:06 -07:00
oss Support BYOK for OSS storage driver 2018-12-25 08:30:40 +08:00
s3-aws S3 Driver: added comment for missing KeyCount workaround 2019-03-15 21:05:21 +01:00
swift swift: correct segment path generation 2019-06-22 23:44:43 -07:00
testdriver context: remove definition of Context 2017-08-11 15:53:31 -07:00
testsuites Fix typo: offest -> offset 2019-04-05 14:20:20 -05:00
fileinfo.go Move storagedriver package to registry/storage/driver 2015-02-11 12:43:04 -08:00
storagedriver.go Introduce Walk Method Per Storage Driver 2018-01-07 22:45:17 -08:00
walk_test.go Ignore missing paths during enumeration 2018-09-05 10:17:08 -07:00
walk.go Ignore missing paths during enumeration 2018-09-05 10:17:08 -07:00