ContextShift, and a cached thread pool for jvm-thread-blocking calls, using
evalOnto make sure those calls happen on the thread blocking pool
evalOn(or related) to put it on the right pool, you risk severely hampering the application's efficiency
@gafiatulin would you mind pulling master into your branch? lendup/fs2-blobstore#49
Looks like Travis is using the
travis.yml from your branch, not master. I thought it would merge master first and use
travis.yml from there. Just trying to get a green build before merging
Btw has anyone seen this problem when using
bufferedPut on an
Failed to reset the request input stream; If the request involves an input stream, the maximum stream buffer size can be configured via request.getRequestClientOptions().setReadLimit(int)
I'm wondering if this is a problem specific to our usage of S3Store or an underlying problem with S3Store, involving puts on large files
bufferedPut. Does it write the entire file to the local filesystem before writing to the output
TransferManager, see the main readme in the repo. E.g.
val awsCredentials = new BasicAWSCredentials(accessKey, secretKey) val credentialsProvider = new AWSStaticCredentialsProvider(awsCredentials) val transferManager = TransferManagerBuilder.standard().withS3Client(AmazonS3ClientBuilder.standard.withCredentials(credentialsProvider).withRegion(region).build) .build
Store[F].putscaladoc is out of date? It looks like
S3Storehas support for multipart uploads when the size of the upload is unknown.