Skip to content

FIX Hive Database connection - TTransportException: TSocket read 0 bytes#7015

Closed
Vity01 wants to merge 1 commit intoapache:masterfrom
Vity01:master
Closed

FIX Hive Database connection - TTransportException: TSocket read 0 bytes#7015
Vity01 wants to merge 1 commit intoapache:masterfrom
Vity01:master

Conversation

@Vity01
Copy link

@Vity01 Vity01 commented Mar 12, 2019

We were unable to connect to our cluster until we added additional dependencies.

We dived into following errors:
SASL Error: no mechanism available: No worthy mechs found
or thrift.transport.TTransport.TTransportException: TSocket read 0 bytes
I found this solution at cloudera/impyla#149 and successfully tested it.

@codecov-io
Copy link

codecov-io commented Mar 12, 2019

Codecov Report

Merging #7015 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #7015   +/-   ##
=======================================
  Coverage   64.46%   64.46%           
=======================================
  Files         421      421           
  Lines       20521    20521           
  Branches     2245     2245           
=======================================
  Hits        13229    13229           
  Misses       7165     7165           
  Partials      127      127

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d308c84...f266bac. Read the comment docs.

@mistercrunch
Copy link
Member

mistercrunch commented Mar 13, 2019

What's the size of the image before/after? We may want to keep optional [heavy] deps in higher layers.

@mistercrunch mistercrunch added the risk:breaking-change Issues or PRs that will introduce breaking changes label Mar 13, 2019
@kristw kristw added the !deprecated-label:bug Deprecated label - Use #bug instead label Mar 13, 2019
@michellethomas
Copy link
Contributor

@mistercrunch can you add context on why this is a breaking change?

@stale
Copy link

stale bot commented May 27, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label May 27, 2019
@stale stale bot closed this Jun 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

!deprecated-label:bug Deprecated label - Use #bug instead inactive Inactive for >= 30 days risk:breaking-change Issues or PRs that will introduce breaking changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants