I think 2.6 failed to abruptly close streams that weren't fully read, which we observed as a huge performance hit. We had to backport the 2.7 improvements before being able to use it.
- s3 bucket access/read file didi
- Re: s3 bucket access/read file spark user
- Re: s3 bucket access/read file Akhil Das
- Re: s3 bucket access/read file didi
- Re: s3 bucket access/read file Exie
- Re: s3 bucket access/read file Aaron Davidson
- Re: s3 bucket access/read file Steve Loughran
- Re: s3 bucket access/read file Aaron Davidson