[jira] [Created] (HBASE-15644) disable precommit scaladoc test

Sean Busbey created HBASE-15644: --- Summary: disable precommit scaladoc test Key: HBASE-15644 URL: https://issues.apache.org/jira/browse/HBASE-15644 Project: HBase Issue Type: Task

Re: [DISCUSS] Shade protobuf so we can move to a newer version

I think we could do it with some maven tricks. Just do not relocate the protobuf things in asyncwal? Move the related classes to a new sub project? Thanks. 2016-04-13 12:26 GMT+08:00 Sean Busbey : > On Tue, Apr 12, 2016 at 6:17 PM, Stack wrote: > > > > > >

[jira] [Created] (HBASE-15643) Need metrics of cache hit ratio for one table

Heng Chen created HBASE-15643: - Summary: Need metrics of cache hit ratio for one table Key: HBASE-15643 URL: https://issues.apache.org/jira/browse/HBASE-15643 Project: HBase Issue Type: Bug

[jira] [Created] (HBASE-15642) split region number for one table on webUI never be reduced

Heng Chen created HBASE-15642: - Summary: split region number for one table on webUI never be reduced Key: HBASE-15642 URL: https://issues.apache.org/jira/browse/HBASE-15642 Project: HBase

Re: [DISCUSS] Shade protobuf so we can move to a newer version

On Tue, Apr 12, 2016 at 6:17 PM, Stack wrote: > > > On an initial pass, the only difficult part seems to be interaction with > HDFS in asyncwal (might just pull in the HDFS messages). > > I have some idea how we can make this work either by pushing asyncwal upstream to HDFS or

[jira] [Created] (HBASE-15641) Shell "alter" should do a single modifyTable operation

Gary Helmling created HBASE-15641: - Summary: Shell "alter" should do a single modifyTable operation Key: HBASE-15641 URL: https://issues.apache.org/jira/browse/HBASE-15641 Project: HBase

Re: [DISCUSS] Shade protobuf so we can move to a newer version

Yeah I think it's a good idea however we need to remove PB from all our user facing api's first. There are some brave souls working on it here: https://issues.apache.org/jira/browse/HBASE-15174 On Tue, Apr 12, 2016 at 4:17 PM, Stack wrote: > I opened HBASE-15638 Shade protobuf

[DISCUSS] Shade protobuf so we can move to a newer version

I opened HBASE-15638 Shade protobuf but should probably raise the larger intent here. You fellows might have an opinion (smile). We need to shade PB so we can move to a different version. We need to move to a different version because we want to save on buffer copies -- newer versions of PB have

[jira] [Created] (HBASE-15638) Shade protobuf

stack created HBASE-15638: - Summary: Shade protobuf Key: HBASE-15638 URL: https://issues.apache.org/jira/browse/HBASE-15638 Project: HBase Issue Type: Bug Components: Protobufs

[jira] [Created] (HBASE-15637) TSHA Thrift-2 server should allow limiting call queue size

Mikhail Antonov created HBASE-15637: --- Summary: TSHA Thrift-2 server should allow limiting call queue size Key: HBASE-15637 URL: https://issues.apache.org/jira/browse/HBASE-15637 Project: HBase

Re: [DISCUSS] No regions on Master node in 2.0

Sorry to be late to the party here. I'll sprinkle my comments over the thread where they make the most sense. > Currently in the master branch, HMaster hosts 'system tables': e.g. > hbase:meta. HMaster is doing more than just gardening the cluster, > bootstrapping and keeping all up and serving

Re: Observed origin/master and origin/Master branches in git

Thanks for the quick action stack! After running "git remote prune origin", now the problem disappears. Best Regards, Yu On 12 April 2016 at 23:15, Stack wrote: > It was there for a while Yu Li. I ran into your problem and removed it > after verifying it had nothing not in

Re: Observed origin/master and origin/Master branches in git

I checked my local repository, and find that when: remote.origin.url= https://git-wip-us.apache.org/repos/asf/hbase.git then the output of "git branch -r | grep -i master" would be: origin/0.90_master_rewrite origin/HEAD -> origin/master origin/master

[jira] [Created] (HBASE-15636) hard coded wait time out value in HBaseTestingUtility#waitUntilAllRegionsAssigned might cause test failure

Stephen Yuan Jiang created HBASE-15636: -- Summary: hard coded wait time out value in HBaseTestingUtility#waitUntilAllRegionsAssigned might cause test failure Key: HBASE-15636 URL:

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: Observed origin/master and origin/Master branches in git

I similarly do not see it listed in our set of head refs: https://git1-us-west.apache.org/repos/asf?p=hbase.git;a=heads On Tue, Apr 12, 2016 at 9:19 AM, Ted Yu wrote: > $ git clone -b Master https://github.com/apache/hbase.git ma > ... > warning: Remote branch Master not

Re: Observed origin/master and origin/Master branches in git

$ git clone -b Master https://github.com/apache/hbase.git ma ... warning: Remote branch Master not found in upstream origin, using HEAD instead Where did you see the Master branch ? On Tue, Apr 12, 2016 at 6:20 AM, Yu Li wrote: > Hi All, > > As titled, there seems to be a new

Observed origin/master and origin/Master branches in git

Hi All, As titled, there seems to be a new origin/Master branch created recently, and when trying to pull the changes, my git client complains: == error: Ref refs/remotes/origin/master is at 90d3b03b674e6718ffcd3eaef00845be5e77656f but expected