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.

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

Make sure we read all data in _read_frame() and _recv_sasl_message() #23

Merged
merged 1 commit into from
Mar 30, 2020

Conversation

Lordshinjo
Copy link
Contributor

@Lordshinjo Lordshinjo commented Mar 13, 2020

  • self._trans.read() usually makes no attempt to read all data, so use
    readAll() instead
  • Keep the compatibility layer with thriftpy, as readAll does not exist
    there, only read, which functions the same as readAll

Fixes #22

- self._trans.read() usually makes no attempt to read all data, so use
readAll() instead
- Keep the compatibility layer with thriftpy, as readAll does not exist
there, only read, which functions the same as readAll

Fixes cloudera#22
@NielsZeilemaker
Copy link

@dknupp is this something you can merge, as it's a bug which was introduced in 0.41

@dknupp
Copy link
Contributor

dknupp commented Mar 30, 2020

@dknupp is this something you can merge, as it's a bug which was introduced in 0.41

Thanks @NielsZeilemaker -- tested to confirm this works. Thank you for the fix.

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.

the new version 0.4.1 will cause pandas read_sql() stuck
3 participants