We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
read_deltalake
read_parquet
I did a quick test reading DeltaLake data in a notebook on a Coiled cluster from s3, with dd.read_parquet vs ddt.read_deltalake.
DeltaLake
dd.read_parquet
ddt.read_deltalake
Cluster: https://cloud.coiled.io/clusters/245026/information?account=dask-engineering.
Data is located in s3://coiled-datasets/delta/.
s3://coiled-datasets/delta/
Results:
This doesn't look good, and needs looking into.
The text was updated successfully, but these errors were encountered:
Second attempt, after merging #57.
Cluster: https://cloud.coiled.io/clusters/245853?account=dask-engineering
Looks like dask-deltalake is doing something very inefficient.
dask-deltalake
Sorry, something went wrong.
No branches or pull requests
I did a quick test reading
DeltaLake
data in a notebook on a Coiled cluster from s3, withdd.read_parquet
vsddt.read_deltalake
.Cluster: https://cloud.coiled.io/clusters/245026/information?account=dask-engineering.
Data is located in
s3://coiled-datasets/delta/
.Results:
This doesn't look good, and needs looking into.
The text was updated successfully, but these errors were encountered: