Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

fix: no longer raise a warning in to_dataframe if max_results set #815

Merged
merged 1 commit into from Jul 27, 2021
Merged

fix: no longer raise a warning in to_dataframe if max_results set #815

merged 1 commit into from Jul 27, 2021

Commits on Jul 27, 2021

  1. fix: a warning is always raised if max_results set 

    That warning should only be used when BQ Storage client is
explicitly passed in to RowIterator methods when max_results
value is also set.
    @plamut
    plamut committed Jul 27, 2021
    Copy the full SHA
    0137cf0 View commit details
    Browse the repository at this point in the history