When we create a S3SeekableByteChannel with option READ, then we should not upload the data on close(). I understand this functionality for other options (like WRITE) when we need to sync the changes with the remote S3, but in this case it is very confusing and decreases the performance of this implementation.
For now I have workarounds for this, but I think this issue deserves some attention in the future.
Hi all,
When we create a
S3SeekableByteChannel
with option READ, then we should not upload the data onclose()
. I understand this functionality for other options (like WRITE) when we need to sync the changes with the remote S3, but in this case it is very confusing and decreases the performance of this implementation.For now I have workarounds for this, but I think this issue deserves some attention in the future.
Cheers, Bogdan