Reading private datasets doesn't result in an error
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 305
- Avg merge
- 22h 37m
- Merged PRs (30d)
- 4
Description
While using Dask I forgot to configure my local AWS credentials when reading a private dataset (see snippet below):
ddf = dd.read_parquet(
"s3://coiled-runtime-ci/nyc-tlc/yellow_tripdata_2019_parquet/yellow_tripdata_2019-*.parquet"
)
This returned an empty DataFrame, which surprised me. Naively I would have expected this to return a permission error (or something similar).
@martindurant I'm not sure if this is an s3fs or dask issue. Happy to move this issue somewhere else if appropriate.
cc @ncclementi for visibility
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the Dask read_parquet example with missing local AWS credentials and inspect whether the empty result originates in s3fs or Dask. No source files or tests are named; identify the responsible layer, then add coverage for the expected permission-error behavior once the intended outcome is confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100