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

Does happybase officially support hbase 1.1.x & 1.2.x? #163

Closed
DeoLeung opened this issue Mar 26, 2017 · 1 comment
Closed

Does happybase officially support hbase 1.1.x & 1.2.x? #163

DeoLeung opened this issue Mar 26, 2017 · 1 comment

Comments

@DeoLeung
Copy link

I'm using happybase==1.0.0 & thriftpy==0.3.9 connecting to hbase=1.1.5

It worked fine at the beginning but recently I stuck with errors in issue:

Thriftpy/thriftpy#283

# start thrift server using default
/opt/hbase-1.1.5/bin/hbase start thrift

# create python connection using default
conn = happybase.Connection(host='xxx', port=9090)
table = conn.table('test_table')
table.scan(...)

# at some uncertain point
/python3.5/site-packages/happybase/table.py in scan(self, row_start, row_stop, row_prefix, columns, filter, timestamp, include_timestamp, batch_size, scan_batching, limit, sorted_columns)
    393                 items = self.connection.client.scannerGetList(
--> 394                     scan_id, how_many)
    395

/python3.5/site-packages/thriftpy/thrift.py in _req(self, _api, *args, **kwargs)
    197         if not getattr(result_cls, "oneway"):
--> 198             return self._recv(_api)
    199

/python3.5/site-packages/thriftpy/thrift.py in _recv(self, _api)
    214             self._iprot.read_message_end()
--> 215             raise x
    216         result = getattr(self._service, _api + "_result")()

<class 'str'>: (<class 'TypeError'>, TypeError('__str__ returned non-string (type bytes)',))

Would it possibly be version incompatible? as I saw compat=0.9.8 in Connection but no 1.x

@wbolster
Copy link
Member

the compat flag is just for thrift api changes (it has been extended a bit over time), and should be upwards compatible.

the error you're seeing happens inside thriftpy, and is likely a bug in that library.

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

No branches or pull requests

2 participants