If you continue using buck, you can refer to the cxx_binary goal of
simple-client in src/hbase/client/BUCK for your own app.
You can also use make. See Makefile under hbase-native-client
Cheers
On Sun, Sep 24, 2017 at 10:06 AM, Andrzej wrote:
> W dniu 24.09.2017 o
[
https://issues.apache.org/jira/browse/HBASE-17249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huaxiang sun resolved HBASE-17249.
--
Resolution: Won't Fix
Yeah, you are right. I change it to wont fix.
> Get/Scan's
[
https://issues.apache.org/jira/browse/HBASE-17249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
huaxiang sun reopened HBASE-17249:
--
> Get/Scan's setTimeRange/setColumnFamilyTimeRange can take the TimeRange
> reference as the
You should run buck under hbase-native-client .
Source files are now under hbase-native-client/src/hbase/ directory.
For building simple-client, you can use:
buck build src/hbase/client:simple-client
For #2, you'd better not mix your code inside native client library.
I build with Maven (after installing Java Oracle 8) and do time
consuming first time start `sudo bin/start-docker.sh`
In file /hbase-native-client/BUILDING.md is:
buck build //core:core
buck test --all
buck build //core:simple-client
But directories structure changes.
Previously was BUCK in
W dniu 24.09.2017 o 18:43, Ted Yu pisze:
For building simple-client, you can use:
buck build src/hbase/client:simple-client
Ok, this built simple-client
For #2, you'd better not mix your code inside native client library.
What is best way use HBase client code in my binary?
The best, would
wuchengzhi created HBASE-18868:
--
Summary: metrics error and the jmx loss many metrics like
'Hadoop:service=HBase,name=RegionServer,sub=IPC'
Key: HBASE-18868
URL: https://issues.apache.org/jira/browse/HBASE-18868
Hi, we have a table which when queried with more than one columkey for a
row key (using addcolumn(colfamily, columkey)), returns cells which are not
present. It returns a empty byte array as value for those cells. Using
debugger we found the timestamp of those cells to *'OLDEST_TIMESTAMP'* and
the
Can you tell us more about this table (e.g. schema) ?
If you can formulate a unit test which reproduces this behavior, that would
be easier to debug.
Which version of hbase are you using ?
Cheers
On Sun, Sep 24, 2017 at 9:30 PM, Karthick Ram
wrote:
> Hi, we have a