You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Trần Tiến Đức (JIRA)" <se...@james.apache.org> on 2019/07/16 10:46:00 UTC

[jira] [Created] (JAMES-2838) [New Vault] CassandraBlobStore should deal with buckets

Trần Tiến Đức created JAMES-2838:
------------------------------------

             Summary: [New Vault] CassandraBlobStore should deal with buckets
                 Key: JAMES-2838
                 URL: https://issues.apache.org/jira/browse/JAMES-2838
             Project: James Server
          Issue Type: Improvement
            Reporter: Trần Tiến Đức


Proposal
Upon default bucket, rely on the existing table (not containing "bucketName")


Introduce some new tables to leverage storage when bucket is specified:

 
{code:java}
BucketedBlobs
 PK BucketName
 PK BlobId
 C chunkCount
BucketedBlobParts
 PK BucketName
 PK BlobId
 CK chunkNumber 
 C data
{code}
 


Benefits: easy to implement


Drawbacks: expensive to delete a Bucket (full blobStore iteration) - Can it be mitigated with a timeSerie allowing blob listing? (this looks like too early anticipation...)



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org