Skip to content

Parse bytes_per_chunk keyword from string#6370

Merged
TomAugspurger merged 1 commit intodask:masterfrom
mrocklin:sql-bytes-per-chunk
Jul 6, 2020
Merged

Parse bytes_per_chunk keyword from string#6370
TomAugspurger merged 1 commit intodask:masterfrom
mrocklin:sql-bytes-per-chunk

Conversation

@mrocklin
Copy link
Member

@mrocklin mrocklin commented Jul 3, 2020

db,
columns=list(df.columns),
bytes_per_chunk=2 ** 30,
bytes_per_chunk="2 GiB",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you test both of these cases, to ensure that we don't regress on accepting integers?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I flopped around some of the current uses of this keyword in the test suite to strings while leaving some others as integers. I think that we're covered in both cases, even if there isn't an explicit test. I can make an explicit test though if preferred.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As long as we have some coverage for passing integers I think we're good.

@TomAugspurger TomAugspurger merged commit bf9d4a4 into dask:master Jul 6, 2020
@TomAugspurger
Copy link
Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants