S3 `get-object` call doesn't coerce correctly about amazonica HOT 3 CLOSED

I spoke too soon about the second example working; the result of the get-object call should contain an object that implements the input stream interface, but amazonica coerces that object into a clojure map, so there is no way to retrieve the data.

Is this something that can be handled with amazonica's reflection or special-cased, or for s3 should I just use the raw Java classes directly?

from amazonica.

Yeah, the S3 namespace has some issues. It's the one package in the Java client library that's not "uniform," i.e. no-arg ctor, public accessors for every property. I'll have some time this weekend to try to get it sorted.

"Is this something that can be handled with amazonica's reflection or special-cased, or for s3 should I just use the raw Java classes directly?"

I'll take care to handle that correctly within the az.aws.s3 namespace. Each of the service-specific namespaces provide facilities to handle coercion (in) and conversion (out). See the dynamodb namespace for an example.

Thanks for the feedback Kevin.

from amazonica.

Awesome, thanks!

from amazonica.