s3" to clients of it.
>
> Using this approach I can get a basic read to work with spark but this has
> numerous drawbacks, including being very fragile, not supporting writes,
> and
> not to mention I'm sure it'll be a huge performance bottleneck once we
> start
> tryi
huge performance bottleneck once we start
trying to run larger workloads ...so... I'd like to get the native s3a/s3n
connectors working if at all possible, but need some help.
Thanks!
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/s3-acc