This is nothing to worry about. jclouds creates temporary files when
HTTP payloads exceed 256 KB to avoid exhausting memory. You can see the
source of this message at
core/src/main/java/org/jclouds/logging/internal/Wire.copy. I believe
that this code is only exercised with debug logging;
Here is an example of unwrapping a compute provider:
https://stackoverflow.com/questions/23044060/how-access-native-provider-api-with-jclouds-1-7
You can unwrap a blobstore provider in the same way.
On Fri, May 22, 2020 at 12:13:31AM -, John Calcote wrote:
> Hi Andrew,
>
> I've searched
Hi Andrew,
I've searched high and low for how to do that "unwrap" trick you mentioned here:
https://jclouds.apache.org/start/concepts/#providers
I've even played with evaluating different methods on the blobstore context and
builder. I cannot find an obvious (or unobvious) way to access the
Hi Andrew,
I've got code that's uploading using the jclouds multi-part abstraction. Here
are the log trace messages for a portion of an upload of a 1G file:
2020-05-21 16:52:07.203 +,36570333402959 {} DEBUG o.j.r.i.InvokeHttpMethod
[cloud-normalpri-4] >> invoking PutObject
2020-05-21
