-
Notifications
You must be signed in to change notification settings - Fork 234
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
error when it scans for hbase #110
Comments
yes, when I modified my Entity to
THERE IS NO PROBLEM YET. |
We are working to add full support on byte[] as a row key in hbase, will update on this JIRA once done. As a work around String can be used as storage will always be in bytes only. -Vviek |
If I want to make a rowkey as a composite key for the better performance of hbase, how could I refect it? I mean that our plan for a rowkey is liek this
cpid, channelid are long type values. for this situation, String typed id is not highly recommended because long typed values could be different length. I mean that long type '1', '10000' has a same length in Long bug different length in String. any ideas? - Henry |
Composite keys support is planned for next release but it's not there as of This means you have to build your primary key (probably by concatenating One approach for long values would be to padding characters keeping length Regards, On Fri, Aug 24, 2012 at 11:14 AM, Henry JunYoung Kim <
|
Is the "Composite keys support" working now for Hbase??? I'm trying to use the example for Cassandra to Hbase, but met an error |
Not yet supported. planned with 2.11 . -Vivek |
Hey Guys, |
It is on road map. Team is working on it. Will post an update soon. |
Opened #603 to enable composite key support for HBase. |
hi, developers.
I have a following method to scan data for hbase.
Scan Method
Sample Entity
in a test-case,
When I executed a test-case, I got the error like this.
internally, it prints out this kinds of traces.
my guess is an error from this.
In a PropertyAccessorHelper.setId(Object entity, EntityMeta metadata, String rowKey)
The text was updated successfully, but these errors were encountered: