-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PseudoKV #67
Comments
To make this slightly more concrete, I was thinking along the lines of: type PseudoS3 struct { ... }
func (PseudoS3) CreateBucket(name string) (*PseudoBucket, error)
func (PseudoS3) Bucket(name string) (*PseudoBucket, error)
type PseudoBucket struct { ... }
func (PseudoBucket) Put(key, val []byte) error
func (PseudoBucket) Get(key []byte) ([]byte, error)
func (PseudoBucket) Delete(key []byte) error
func (PseudoBucket) Sync() error The main goal would be to aggregate |
I think it also needs |
I think it'd be better to call this interface |
It also would be better if the type of |
PseudoKV has been integrated, moving new roadmap features to #126 for consistency. |
I think PseudoKV isn't done yet. There are still some missing functions: us/renter/renterutil/metadb.go Lines 348 to 354 in 8a2eb34
us/renter/renterutil/metadb.go Lines 367 to 369 in 8a2eb34
Also |
Thanks, reopened. I see this is also related to #102 correct? |
Yes, it is. Especially, this problem #102 (comment). |
Moving this here-->
The metafile format was designed to store ordinary user files, and PseudoFS was designed to represent an ordinary filesystem. Neither of them will work optimally with an S3 bucket architecture. It sounds like we should investigate creating something like a "PseudoS3" that is better geared towards key-value storage.
The text was updated successfully, but these errors were encountered: