[jira] [Created] (HBASE-15211) Don't run the CatalogJanitor if there are regions in transition

Elliott Clark created HBASE-15211: - Summary: Don't run the CatalogJanitor if there are regions in transition Key: HBASE-15211 URL: https://issues.apache.org/jira/browse/HBASE-15211 Project: HBase

Successful: HBase Generate Website

Build status: Successful If successful, the website and docs have been generated. If failed, skip to the bottom of this email. Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If you prefer to keep the hbase-site repo around

RE: HBASE Table/schema design resource.

Hello Keith, Now HBase has a MOB feature in trunk (HBASE-11339), but it is not in any release branch. It might be merged back to 1.3 or 1.4 later. If your blob size is large (100KB-10MB), you could try this. In table design with this feature, you could store the blob in a single column family

[DISCUSS] Dynamic switches in master

This came up in the review for HBASE-15128, but we thought that we should surface this discussion in dev@. The idea for HBASE-15128 is that, we should have a dynamic switch in master so that the operator (or HBCK) can disable all region splits or merges. We currently have such dynamic switches

HBASE Table/schema design resource.

I have json hierarchical data blobs that I want to store to HBASE. What are the good books / resources out there on table / schema design. Particularly I want to know what are the best practices for storing repeated columns, nested entities, store them as sub json blob... Thanks, keith

Re: [DISCUSS] Dynamic switches in master

+1 to reducing dependency on zookeeper > On Feb 3, 2016, at 9:50 PM, 张铎 wrote: > > My opinion, use conf file as default, and use code to override the config > in conf file. > And we need to persist the overridden value somewhere, not zk I'd say. I > agree with Matteo

Re: [DISCUSS] Dynamic switches in master

Looked through the comments and glanced at the patch. I generally think that the patch addressing specific existing problem shouldn't be blocked on generic big feature like dynamic configuration framework, so would be good to get something committable sooner rather then latter. It seems the only

[jira] [Created] (HBASE-15212) RRCServer should enforce max request size

Enis Soztutar created HBASE-15212: - Summary: RRCServer should enforce max request size Key: HBASE-15212 URL: https://issues.apache.org/jira/browse/HBASE-15212 Project: HBase Issue Type:

Re: [DISCUSS] Dynamic switches in master

My opinion, use conf file as default, and use code to override the config in conf file. And we need to persist the overridden value somewhere, not zk I'd say. I agree with Matteo that we should reduce the dependency of zk. Maybe we could introduce an hbase:config table? And for the dynamic

Re: integration with HDFS centralized caching

Thanks Stack. Sorry to hear that didn't work out. Oh well. On Tue, Feb 2, 2016 at 9:54 PM Stack wrote: > On Tue, Feb 2, 2016 at 6:03 PM, Jesse Yates > wrote: > > > Hey all, > > > > I poked around a bit in the archives and in JIRA (as well as random >