1 Answer
- Newest
- Most votes
- Most comments
0
I ran into the same issue. For me, the solution was to switch from using the "s3a" URI schema to just "s3" when reading files.
I went from this
df = spark.read.json('s3a://...')
to this
df = spark.read.json('s3://...')
Hope this helps
answered 2 years ago
Relevant content
- asked a year ago
- asked 7 years ago
- Accepted Answer
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago