Re: jClouds 2.0 MultiPart Upload

:37 AM To: user@jclouds.apache.org Subject: Re: jClouds 2.0 MultiPart Upload Does it mean if we are not specifying executorservice, the upload happens in sequential ? Regards Archana On Saturday, 4 February 2017, 10:34, Andrew Gaul <g...@apache.org> wrote: PutOptions *takes* an Exe

Re: jClouds 2.0 MultiPart Upload

Does it mean if we are not specifying  executorservice, the upload happens in sequential ? Regards Archana On Saturday, 4 February 2017, 10:34, Andrew Gaul wrote: PutOptions *takes* an ExecutorService which allows multiple threads to concurrently upload multiple

Re: jClouds 2.0 MultiPart Upload

PutOptions *takes* an ExecutorService which allows multiple threads to concurrently upload multiple parts. On Sat, Feb 04, 2017 at 03:34:30AM +, Archana C wrote: > Hi > > I think the question was not clear. Parallel upload of multiple file is fine > and that can be achieved by using

Re: jClouds 2.0 MultiPart Upload

Hi I think the question was not clear. Parallel upload of multiple file is fine and that can be achieved by using executorservice. The question here is, does multipartUpload i.e uploading of each part is happening in parallel ? Does sequential upload of part deprecated ? RegardsArchana

Re: jClouds 2.0 MultiPart Upload

Hi Is SequentialMultiPartUpload deprecated in jClouds2.0. Is all the multipart uploads are parallel now ? RegardsArchana On Friday, 3 February 2017, 18:39, Archana C wrote: Thanks it helped RegardsArchana On Friday, 3 February 2017, 12:06, Ignasi Barrera

Re: jClouds 2.0 MultiPart Upload

It looks like the OOM exception is thrown when writing the wire logs. When using the blob store apis you might see binary data in the logs, as the "jclouds.wire" logger logs the response/request payloads which might be huge for some blobs and can cause this kind of exceptions. Could you try

jClouds 2.0 MultiPart Upload

Hi I have written a sample code for multipart upload using jClouds-2.0     Properties overrides = new Properties();         BlobStoreContext context = ContextBuilder.newBuilder("openstack-swift")                 .endpoint("http://x.xxx.xx.xx:5000/v2.0;)                 .credentials("xx:xx",