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

Getting cybin.ProtocolError: No protocol version header error #161

Closed
phonchi opened this issue Mar 10, 2017 · 3 comments
Closed

Getting cybin.ProtocolError: No protocol version header error #161

phonchi opened this issue Mar 10, 2017 · 3 comments

Comments

@phonchi
Copy link

@phonchi phonchi commented Mar 10, 2017

My happybase version is 1.00 and hbase version is 1.21. According to the documentation, the connection can be established using the following commands

connection = happybase.Connection('hostname')

I have already start hbase thrift server using

hbase thrift start

and confirms that the 9090 port is listening by ThriftServer.

But I still getting following error when I execute print(connection.tables())

File "thriftpy/protocol/cybin/cybin.pyx", line 439, in cybin.TCyBinaryProtocol.read_message_begin (thriftpy/protocol/cybin/cybin.c:6400)
cybin.ProtocolError: No protocol version header

I think the default parameters port, transport should work for my environment describing above.

Any suggestion is appreciated!!

@wbolster
Copy link
Member

@wbolster wbolster commented Mar 10, 2017

usually errors like these are indeed caused by a wrong transport configuration.

do pre-1.0 happybase versions work? (different thrift library)

Loading

@phonchi
Copy link
Author

@phonchi phonchi commented Mar 10, 2017

After changing some setting in hbase-site.xml it works now!! I remove the following property:

<property>
  <name>hbase.regionserver.thrift.http</name>
  <value>true</value>
</property>
<property>
  <name>hbase.thrift.support.proxyuser</name>
  <value>true/value>
</property>

I am not sure whether these properties should be set or not. Anyway, thanks for your help!!

Loading

@wbolster
Copy link
Member

@wbolster wbolster commented Mar 11, 2017

great!

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants