Hooray docs!
On Aug 20, 2014 10:25 AM, Esteban Gutierrez este...@cloudera.com wrote:
+1 thank you for all the hard work Misty!
esteban.
--
Cloudera, Inc.
On Wed, Aug 20, 2014 at 10:20 AM, Andrew Purtell apurt...@apache.org
wrote:
Huge +1
On Tue, Aug 19, 2014 at 10:53 PM,
Could you explain a bit more of why you don't want a memstore? I can't see
why it is harmful. Sorry to be dense.
On Aug 3, 2014 11:24 AM, Ozhan Gulen ozhangu...@gmail.com wrote:
Hello,
In our hbase cluster memstore flush size is 128 mb. And to insert data to
tables, we only use bulk load tool.
Giuseppe,
As far as metrics go:
If you want a monitoring solution which doesn't require HBase for
course grain metrics I highly recommend graphite. It has become a bit
of an industry standard and you may find your ops guy already has it
setup. OpenTSDB requires HBase as it's datastore but is an
, 2013, Alex Newman wrote:
Based on the previous work using async libraries to index HBase into
elastic search, I've created.
https://github.com/posix4e/Elasticsearch-HBase-River
This river uses the replication feature in HBase to replicate into
elastic search which means it's harder to setup
Based on the previous work using async libraries to index HBase into
elastic search, I've created.
https://github.com/posix4e/Elasticsearch-HBase-River
This river uses the replication feature in HBase to replicate into
elastic search which means it's harder to setup, but works way more
