[
https://issues.apache.org/jira/browse/JCLOUDS-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019393#comment-16019393
]
Rishika commented on JCLOUDS-1280:
----------------------------------
I plan to submit pull request for this. Based on description given here is my
proposed flow:
1. Create a separate class that initializes default mpu part size( or retains
to some default (32MB??))
2. user-defined classes to guice inject to this new class and overrides default
mpu part size via jclouds.mpu.parts.size property(set as part of
ContextBuilder.overrides)
3. MultipartUploadSlicingAlgorithm class to read min, max and default values
from this new class
4. BaseBlobStore will as usual instantiate MultipartUploadSlicingAlgorithm
If required min and max can also be provisioned to be overridden?
> Allow configuration of multi-part upload part sizes
> ---------------------------------------------------
>
> Key: JCLOUDS-1280
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1280
> Project: jclouds
> Issue Type: New Feature
> Components: jclouds-blobstore
> Affects Versions: 2.0.1
> Reporter: Andrew Gaul
>
> Presently {{BaseBlobStore}} instantiates {{MultipartUploadSlicingAlgorithm}}
> directly, providing it minimum and maximum values for parts. Instead it
> should Guice inject this object which would allow overriding values like
> {{defaultPartSize}} via setting {{jclouds.mpu.parts.size}} in
> {{ContextBuilder.overrides}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
