[jira] [Created] (HBASE-19186) Unify to use bytes to show size in master/rs ui

2017-11-04 Thread Guanghao Zhang (JIRA)
Guanghao Zhang created HBASE-19186: -- Summary: Unify to use bytes to show size in master/rs ui Key: HBASE-19186 URL: https://issues.apache.org/jira/browse/HBASE-19186 Project: HBase Issue

Re: DISCUSSION: Minimum hbase1 version from which you can upgrade to hbase2 (1.2.x?)

2017-11-04 Thread Stack
On Sat, Nov 4, 2017 at 6:19 PM, Guanghao Zhang wrote: > Our internal branch is based on 0.98. And we plan rolling to 2.0. So I will > take a try for rolling from 0.98 to 2.0. But we take a lot backport to our > internal branch, like async client, netty rpc client, serial

[jira] [Resolved] (HBASE-19167) RowCounter not working on 2.0.0-alpha3

2017-11-04 Thread Chia-Ping Tsai (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-19167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved HBASE-19167. Resolution: Duplicate The error doesn't happen in alpha4, but there are other classes

[jira] [Created] (HBASE-19185) ClassNotFoundException: com.fasterxml.jackson.*

2017-11-04 Thread Chia-Ping Tsai (JIRA)
Chia-Ping Tsai created HBASE-19185: -- Summary: ClassNotFoundException: com.fasterxml.jackson.* Key: HBASE-19185 URL: https://issues.apache.org/jira/browse/HBASE-19185 Project: HBase Issue

[jira] [Resolved] (HBASE-19131) Add the ClusterStatus hook and cleanup other hooks which can be replaced by ClusterStatus hook

2017-11-04 Thread Chia-Ping Tsai (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-19131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved HBASE-19131. Resolution: Fixed Hadoop Flags: Reviewed Push to branch-1.4, branch-1, branch-2, and

[jira] [Created] (HBASE-19184) clean up nightly source artifact test to match expectations from switch to git-archive

2017-11-04 Thread Sean Busbey (JIRA)
Sean Busbey created HBASE-19184: --- Summary: clean up nightly source artifact test to match expectations from switch to git-archive Key: HBASE-19184 URL: https://issues.apache.org/jira/browse/HBASE-19184

[jira] [Resolved] (HBASE-19152) Update refguide 'how to build an RC' and the make_rc.sh script

2017-11-04 Thread Sean Busbey (JIRA)
[ https://issues.apache.org/jira/browse/HBASE-19152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey resolved HBASE-19152. - Resolution: Fixed filed HBASE-19184 > Update refguide 'how to build an RC' and the make_rc.sh

Re: DISCUSSION: Minimum hbase1 version from which you can upgrade to hbase2 (1.2.x?)

2017-11-04 Thread Guanghao Zhang
Our internal branch is based on 0.98. And we plan rolling to 2.0. So I will take a try for rolling from 0.98 to 2.0. But we take a lot backport to our internal branch, like async client, netty rpc client, serial replication, throttling, some replication improvements and so on. So our rolling

Re: Empty hbase-shaded-client JAR file

2017-11-04 Thread Sean Busbey
Between the addition of the shaded jars in 1.1.0 and 1.1.1/1.2.0 building the shaded jars was moved to the release profile after complaints about how much time was added to the build by doing them all the time. I think all the discussion was on JIRA:

[jira] [Created] (HBASE-19183) Removed redundant groupId from Maven modules

2017-11-04 Thread Jan Hentschel (JIRA)
Jan Hentschel created HBASE-19183: - Summary: Removed redundant groupId from Maven modules Key: HBASE-19183 URL: https://issues.apache.org/jira/browse/HBASE-19183 Project: HBase Issue Type:

Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available

2017-11-04 Thread Jean-Marc Spaggiari
Thanks for your reply Stack. I will get ready to test the next version. Excited to see 2.0 coming out 2017-11-04 14:44 GMT-04:00 Stack : > On Sat, Nov 4, 2017 at 1:45 AM, Jean-Marc Spaggiari < > jean-m...@spaggiari.org > > wrote: > > > Folks, are you able to run the tests?

Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available

2017-11-04 Thread Stack
On Sat, Nov 4, 2017 at 1:45 AM, Jean-Marc Spaggiari wrote: > Folks, are you able to run the tests? > > I'm trying to run this: > > mvn test -P runAllTests -Dsurefire.secondPartThreadCount=2 > -Dtest.build.data.basedirectory=/ram4G > > > But I'm not able to get it

Re: DISCUSSION: Minimum hbase1 version from which you can upgrade to hbase2 (1.2.x?)

2017-11-04 Thread Stack
On Fri, Nov 3, 2017 at 9:01 PM, Guanghao Zhang wrote: > Can we rolling from 0.98 and 1.1 to 1.2? If this rolling is ok, user can > rolling to 2.0 by two steps, 0.98 to 1.2, then 1.2 to 2.0. > > Yes. They could do that. Would be a pain. Might be able to go from 0.98 to 2.0

Re: DISCUSSION: Minimum hbase1 version from which you can upgrade to hbase2 (1.2.x?)

2017-11-04 Thread Stack
On Fri, Nov 3, 2017 at 8:25 PM, Nick Dimiduk wrote: > 1.2 is good, but are we aware of anything that precludes 1.1? 0.98? On disk > compatibility (HFile, WAL, AMv2) should be the limiting factor here, right? > Wire protocols have been compatible all the while... > > I don't

[jira] [Created] (HBASE-19182) Add deprecation in branch-1 for hbase-prefix-tree so some heads up it removed in hbase2

2017-11-04 Thread stack (JIRA)
stack created HBASE-19182: - Summary: Add deprecation in branch-1 for hbase-prefix-tree so some heads up it removed in hbase2 Key: HBASE-19182 URL: https://issues.apache.org/jira/browse/HBASE-19182 Project:

[jira] [Created] (HBASE-19181) LogRollBackupSubprocedure will fail if we use AsyncFSWAL instead of FSHLog

2017-11-04 Thread Duo Zhang (JIRA)
Duo Zhang created HBASE-19181: - Summary: LogRollBackupSubprocedure will fail if we use AsyncFSWAL instead of FSHLog Key: HBASE-19181 URL: https://issues.apache.org/jira/browse/HBASE-19181 Project: HBase

Re: [VOTE] First hbase-2.0.0-alpha4 Release Candidate is available

2017-11-04 Thread Jean-Marc Spaggiari
Folks, are you able to run the tests? I'm trying to run this: mvn test -P runAllTests -Dsurefire.secondPartThreadCount=2 -Dtest.build.data.basedirectory=/ram4G But I'm not able to get it running completely. It always fails somewhere, never in the same place. How are you running the tests, if