[jira] [Assigned] (HBASE-15597) Clean up configuration keys used in hbase-spark module

2017-01-14 Thread Jerry He (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-15597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jerry He reassigned HBASE-15597:


Assignee: Jerry He

> Clean up configuration keys used in hbase-spark module
> --
>
> Key: HBASE-15597
> URL: https://issues.apache.org/jira/browse/HBASE-15597
> Project: HBase
>  Issue Type: Bug
>  Components: spark
>Affects Versions: 2.0.0
>Reporter: Sean Busbey
>Assignee: Jerry He
>Priority: Critical
> Fix For: 2.0.0
>
>
> This should be considered a blocker for backport to branch-1 since it will 
> impact our compatibility.
> The constants we expose in configuration should all start with "hbase". Since 
> our configurations keys for the spark integration all relate to that system, 
> the prefix for all configuration keys (excluding those cases where we need to 
> do something special due to restrictions in how properties are handled by 
> e.g. spark) should be "hbase.spark".
> Before publishing a public api labeled version of our spark integration we 
> should review all of our configuration keys to make sure they either conform 
> to the "hbase.spark" prefix or they have a comment documenting why they need 
> to be otherwise.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Assigned] (HBASE-14375) define public API for spark integration module

2017-01-14 Thread Jerry He (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-14375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jerry He reassigned HBASE-14375:


Assignee: Jerry He

> define public API for spark integration module
> --
>
> Key: HBASE-14375
> URL: https://issues.apache.org/jira/browse/HBASE-14375
> Project: HBase
>  Issue Type: Task
>  Components: spark
>Reporter: Sean Busbey
>Assignee: Jerry He
>Priority: Blocker
> Fix For: 2.0.0
>
>
> before we can put the spark integration module into a release, we need to 
> annotate its public api surface.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-13652) Case-insensitivity of file system affects table creation

2017-01-14 Thread Xuesen Liang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Xuesen Liang updated HBASE-13652:
-
Attachment: HBASE-13652.master.005.patch

[~esteban], thanks very much for your review.
I think add a flag in configuration is better. HBASE-13652.master.005.patch is 
a corresponding new patch.


> Case-insensitivity of file system affects table creation
> 
>
> Key: HBASE-13652
> URL: https://issues.apache.org/jira/browse/HBASE-13652
> Project: HBase
>  Issue Type: Bug
>  Components: shell
>Affects Versions: 1.0.0
> Environment: HBase standalone mode on Mac OS X.
>Reporter: Lars George
>Assignee: Xuesen Liang
>  Labels: beginner
> Fix For: 2.0.0
>
> Attachments: HBASE-13652.master.001.patch, 
> HBASE-13652.master.002.patch, HBASE-13652.master.003.patch, 
> HBASE-13652.master.004.patch, HBASE-13652.master.005.patch
>
>
> I noticed this on my Mac OS machine:
> {noformat}
> hbase(main):003:0> list
> TABLE 
>   
>
> 0 row(s) in 0.0260 seconds
> => []
> hbase(main):004:0> create 'TestTable', 'info'
> 0 row(s) in 0.2830 seconds
> => Hbase::Table - TestTable
> hbase(main):005:0> create 'testtable', 'colfam1'
> 0 row(s) in 0.1750 seconds
> => Hbase::Table - testtable
> hbase(main):006:0> list
> TABLE 
>   
>
> TestTable 
>   
>
> TestTable 
>   
>
> 2 row(s) in 0.0170 seconds
> => ["TestTable", "TestTable"]
> hbase(main):007:0> status 'detailed'
> version 1.0.0
> 0 regionsInTransition
> master coprocessors: []
> 1 live servers
> de1-app-mba-1.internal.larsgeorge.com:58824 1431124680152
> requestsPerSecond=0.0, numberOfOnlineRegions=4, usedHeapMB=47, 
> maxHeapMB=4062, numberOfStores=4, numberOfStorefiles=0, 
> storefileUncompressedSizeMB=0, storefileSizeMB=0, memstoreSizeMB=0, 
> storefileIndexSizeMB=0, readRequestsCount=16, writeRequestsCount=8, 
> rootIndexSizeKB=0, totalStaticIndexSizeKB=0, totalStaticBloomSizeKB=0, 
> totalCompactingKVs=0, currentCompactedKVs=0, compactionProgressPct=NaN, 
> coprocessors=[]
> "TestTable,,1431124762491.cb30b003b192aa1d429e5a8e908a2f7d."
> numberOfStores=1, numberOfStorefiles=0, 
> storefileUncompressedSizeMB=0, storefileSizeMB=0, memstoreSizeMB=0, 
> storefileIndexSizeMB=0, readRequestsCount=0, writeRequestsCount=0, 
> rootIndexSizeKB=0, totalStaticIndexSizeKB=0, totalStaticBloomSizeKB=0, 
> totalCompactingKVs=0, currentCompactedKVs=0, compactionProgressPct=NaN, 
> completeSequenceId=-1, dataLocality=0.0
> "hbase:meta,,1"
> numberOfStores=1, numberOfStorefiles=0, 
> storefileUncompressedSizeMB=0, storefileSizeMB=0, memstoreSizeMB=0, 
> storefileIndexSizeMB=0, readRequestsCount=10, writeRequestsCount=6, 
> rootIndexSizeKB=0, totalStaticIndexSizeKB=0, totalStaticBloomSizeKB=0, 
> totalCompactingKVs=0, currentCompactedKVs=0, compactionProgressPct=NaN, 
> completeSequenceId=-1, dataLocality=0.0
> "hbase:namespace,,1431124686536.42728f3a3411b0d8ff21c7a2622d9378."
> numberOfStores=1, numberOfStorefiles=0, 
> storefileUncompressedSizeMB=0, storefileSizeMB=0, memstoreSizeMB=0, 
> storefileIndexSizeMB=0, readRequestsCount=6, writeRequestsCount=2, 
> rootIndexSizeKB=0, totalStaticIndexSizeKB=0, totalStaticBloomSizeKB=0, 
> totalCompactingKVs=0, currentCompactedKVs=0, compactionProgressPct=NaN, 
> completeSequenceId=-1, dataLocality=0.0
> "testtable,,1431124773352.8d461d5069d1c88bc3b26562ab30e333."
> numberOfStores=1, numberOfStorefiles=0, 
> storefileUncompressedSizeMB=0, storefileSizeMB=0, memstoreSizeMB=0, 
> storefileIndexSizeMB=0, readRequestsCount=0, writeRequestsCount=0, 
> rootIndexSizeKB=0, totalStaticIndexSizeKB=0, totalStaticBloomSizeKB=0, 
> totalCompactingKVs=0, currentCompactedKVs=0, compactionProgressPct=NaN, 
> completeSequenceId=-1, dataLocality=0.0
> 0 dead servers
> {noformat}
> and on the file system there is 
> {noformat}
> larsgeorge:~$ ls -l hbase/data/default/
> total 0
> drwxr-xr-x  7 larsgeorge  staff  238 May  8 15:39 TestTable
> {noformat}
> This should not happen on a case sensitive file system (I presume), so is of 
> marginal importance. But a simple extra check during directory creation could 
> fix 

[jira] [Updated] (HBASE-17470) Remove merge region code from region server

2017-01-14 Thread Stephen Yuan Jiang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-17470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Yuan Jiang updated HBASE-17470:
---
Status: Patch Available  (was: Open)

> Remove merge region code from region server
> ---
>
> Key: HBASE-17470
> URL: https://issues.apache.org/jira/browse/HBASE-17470
> Project: HBase
>  Issue Type: Sub-task
>  Components: regionserver
>Affects Versions: 2.0.0
>Reporter: Stephen Yuan Jiang
>Assignee: Stephen Yuan Jiang
> Fix For: 2.0.0
>
> Attachments: HBASE-17470.v1-master.patch
>
>
> HBASE-16119 moves the merge region to the master-side.  There is no need to 
> keep region_server-side merge region code to remove logic duplication.  
> util.Merge and HMerge tools depends on RS-side merge region logic.  However, 
> now we can merge regions using shell command.  It is dangerous to do offline 
> merge.  For 2.0, it is a good time to remove those out-of-date tools.   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-17470) Remove merge region code from region server

2017-01-14 Thread Stephen Yuan Jiang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-17470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stephen Yuan Jiang updated HBASE-17470:
---
Attachment: HBASE-17470.v1-master.patch

> Remove merge region code from region server
> ---
>
> Key: HBASE-17470
> URL: https://issues.apache.org/jira/browse/HBASE-17470
> Project: HBase
>  Issue Type: Sub-task
>  Components: regionserver
>Affects Versions: 2.0.0
>Reporter: Stephen Yuan Jiang
>Assignee: Stephen Yuan Jiang
> Fix For: 2.0.0
>
> Attachments: HBASE-17470.v1-master.patch
>
>
> HBASE-16119 moves the merge region to the master-side.  There is no need to 
> keep region_server-side merge region code to remove logic duplication.  
> util.Merge and HMerge tools depends on RS-side merge region logic.  However, 
> now we can merge regions using shell command.  It is dangerous to do offline 
> merge.  For 2.0, it is a good time to remove those out-of-date tools.   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (HBASE-17470) Remove merge region code from region server

2017-01-14 Thread Stephen Yuan Jiang (JIRA)
Stephen Yuan Jiang created HBASE-17470:
--

 Summary: Remove merge region code from region server
 Key: HBASE-17470
 URL: https://issues.apache.org/jira/browse/HBASE-17470
 Project: HBase
  Issue Type: Sub-task
  Components: regionserver
Affects Versions: 2.0.0
Reporter: Stephen Yuan Jiang
Assignee: Stephen Yuan Jiang


HBASE-16119 moves the merge region to the master-side.  There is no need to 
keep region_server-side merge region code to remove logic duplication.  

util.Merge and HMerge tools depends on RS-side merge region logic.  However, 
now we can merge regions using shell command.  It is dangerous to do offline 
merge.  For 2.0, it is a good time to remove those out-of-date tools.   





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-17437) Support specifying a WAL directory outside of the root directory

2017-01-14 Thread Ted Yu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-17437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15823013#comment-15823013
 ] 

Ted Yu commented on HBASE-17437:


To fix the javadoc warnings, see:
http://stackoverflow.com/questions/23337649/unexpected-result-for-value-in-javadoc

> Support specifying a WAL directory outside of the root directory
> 
>
> Key: HBASE-17437
> URL: https://issues.apache.org/jira/browse/HBASE-17437
> Project: HBase
>  Issue Type: Improvement
>  Components: Filesystem Integration, wal
>Affects Versions: 1.2.4
>Reporter: Yishan Yang
>Assignee: Zach York
>  Labels: patch
> Fix For: 2.0.0, 1.4.0
>
> Attachments: hbase-17437-branch-1.2.patch, 
> HBASE-17437.master.001.patch, HBASE-17437.master.002.patch, 
> hbase-17437-master.patch
>
>
> Currently, the WAL and the StoreFiles need to be on the same FileSystem. Some 
> FileSystems (such as Amazon S3) don’t support append or consistent writes. 
> These two properties are imperative for the WAL in order to avoid loss of 
> writes. However, StoreFiles don’t necessarily need the same consistency 
> guarantees (since writes are cached locally and if writes fail, they can 
> always be replayed from the WAL).
>  
> This JIRA aims to allow users to configure a log directory (for WALs) that is 
> outside of the root directory or even in a different FileSystem. The default 
> value will still put the log directory under the root directory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-17426) Inconsistent environment variable names for enabling JMX

2017-01-14 Thread Ted Yu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-17426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822961#comment-15822961
 ] 

Ted Yu commented on HBASE-17426:


We should continue to support HBASE_JMX_OPTS - some users may have used it.

In bin/hbase-config.sh, we should also check the value of HBASE_JMX_BASE:
* if value for HBASE_JMX_BASE is empty, keep current behavior.
* if HBASE_JMX_OPTS is not empty, keep current behavior.
* otherwise use the value of HBASE_JMX_BASE

> Inconsistent environment variable names for enabling JMX
> 
>
> Key: HBASE-17426
> URL: https://issues.apache.org/jira/browse/HBASE-17426
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>
> In conf/hbase-env.sh :
> {code}
> # export HBASE_JMX_BASE="-Dcom.sun.management.jmxremote.ssl=false 
> -Dcom.sun.management.jmxremote.authenticate=false"
> # If you want to configure BucketCache, specify '-XX: MaxDirectMemorySize=' 
> with proper direct memory size
> # export HBASE_THRIFT_OPTS="$HBASE_JMX_BASE 
> -Dcom.sun.management.jmxremote.port=10103"
> {code}
> But in bin/hbase-config.sh , a different variable is used:
> {code}
> # Thrift JMX opts
> if [ -n "$HBASE_JMX_OPTS" ] && [ -z "$HBASE_THRIFT_JMX_OPTS" ]; then
>   HBASE_THRIFT_JMX_OPTS="$HBASE_JMX_OPTS 
> -Dcom.sun.management.jmxremote.port=10103"
> fi
> {code}
> The variable names should be aligned for better user experience.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-17418) Use isEmpty instead of size() == 0 in hbase-rsgroup

2017-01-14 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-17418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822912#comment-15822912
 ] 

Hadoop QA commented on HBASE-17418:
---

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 17s 
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s 
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 
0s {color} | {color:green} The patch appears to include 1 new or modified test 
files. {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m 
40s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 15s 
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 
15s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 
14s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 
32s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 16s 
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 0m 
16s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m 15s 
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m 15s 
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 
14s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 
14s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
28m 50s {color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 0m 
37s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 15s 
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 0m 19s 
{color} | {color:green} hbase-rsgroup in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 
8s {color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 36m 56s {color} 
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.11.2 Server=1.11.2 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12847504/HBASE-17418.master.001.patch
 |
| JIRA Issue | HBASE-17418 |
| Optional Tests |  asflicense  javac  javadoc  unit  findbugs  hadoopcheck  
hbaseanti  checkstyle  compile  |
| uname | Linux b32d0a585a25 3.13.0-105-generic #152-Ubuntu SMP Fri Dec 2 
15:37:11 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | master / 4cb09a4 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HBASE-Build/5261/testReport/ |
| modules | C: hbase-rsgroup U: hbase-rsgroup |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/5261/console |
| Powered by | Apache Yetus 0.3.0   http://yetus.apache.org |


This message was automatically generated.



> Use isEmpty instead of size() == 0 in hbase-rsgroup
> ---
>
> Key: HBASE-17418
> URL: https://issues.apache.org/jira/browse/HBASE-17418
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: HBASE-17418.master.001.patch
>
>
> Use {code:java}.isEmpty(){code} instead 

[jira] [Work started] (HBASE-17469) Properly handle empty TableName in TablePermission#readFields and #write

2017-01-14 Thread Manjunath Anand (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-17469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on HBASE-17469 started by Manjunath Anand.
---
> Properly handle empty TableName in TablePermission#readFields and #write
> 
>
> Key: HBASE-17469
> URL: https://issues.apache.org/jira/browse/HBASE-17469
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Manjunath Anand
>
> HBASE-17450 handles the empty table name in equals().
> This JIRA is to properly handle empty TableName in 
> TablePermission#readFields() and TablePermission#write() methods.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-17469) Properly handle empty TableName in TablePermission#readFields and #write

2017-01-14 Thread Manjunath Anand (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-17469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822900#comment-15822900
 ] 

Manjunath Anand commented on HBASE-17469:
-

Sure thanks [~yuzhih...@gmail.com]. Will come up with a patch soon

> Properly handle empty TableName in TablePermission#readFields and #write
> 
>
> Key: HBASE-17469
> URL: https://issues.apache.org/jira/browse/HBASE-17469
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Manjunath Anand
>
> HBASE-17450 handles the empty table name in equals().
> This JIRA is to properly handle empty TableName in 
> TablePermission#readFields() and TablePermission#write() methods.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-17426) Inconsistent environment variable names for enabling JMX

2017-01-14 Thread Ted Yu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-17426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822895#comment-15822895
 ] 

Ted Yu commented on HBASE-17426:


You're welcome to take this one.

HBASE_JMX_BASE is mentioned by:
http://hbase.apache.org/book.html#jmx_config

We should adhere to HBASE_JMX_BASE.

> Inconsistent environment variable names for enabling JMX
> 
>
> Key: HBASE-17426
> URL: https://issues.apache.org/jira/browse/HBASE-17426
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>
> In conf/hbase-env.sh :
> {code}
> # export HBASE_JMX_BASE="-Dcom.sun.management.jmxremote.ssl=false 
> -Dcom.sun.management.jmxremote.authenticate=false"
> # If you want to configure BucketCache, specify '-XX: MaxDirectMemorySize=' 
> with proper direct memory size
> # export HBASE_THRIFT_OPTS="$HBASE_JMX_BASE 
> -Dcom.sun.management.jmxremote.port=10103"
> {code}
> But in bin/hbase-config.sh , a different variable is used:
> {code}
> # Thrift JMX opts
> if [ -n "$HBASE_JMX_OPTS" ] && [ -z "$HBASE_THRIFT_JMX_OPTS" ]; then
>   HBASE_THRIFT_JMX_OPTS="$HBASE_JMX_OPTS 
> -Dcom.sun.management.jmxremote.port=10103"
> fi
> {code}
> The variable names should be aligned for better user experience.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-17426) Inconsistent environment variable names for enabling JMX

2017-01-14 Thread ChiaPing Tsai (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-17426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822893#comment-15822893
 ] 

ChiaPing Tsai commented on HBASE-17426:
---

Can i take this issue? Which one is better? Should the document be updated in 
the patch?

> Inconsistent environment variable names for enabling JMX
> 
>
> Key: HBASE-17426
> URL: https://issues.apache.org/jira/browse/HBASE-17426
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>
> In conf/hbase-env.sh :
> {code}
> # export HBASE_JMX_BASE="-Dcom.sun.management.jmxremote.ssl=false 
> -Dcom.sun.management.jmxremote.authenticate=false"
> # If you want to configure BucketCache, specify '-XX: MaxDirectMemorySize=' 
> with proper direct memory size
> # export HBASE_THRIFT_OPTS="$HBASE_JMX_BASE 
> -Dcom.sun.management.jmxremote.port=10103"
> {code}
> But in bin/hbase-config.sh , a different variable is used:
> {code}
> # Thrift JMX opts
> if [ -n "$HBASE_JMX_OPTS" ] && [ -z "$HBASE_THRIFT_JMX_OPTS" ]; then
>   HBASE_THRIFT_JMX_OPTS="$HBASE_JMX_OPTS 
> -Dcom.sun.management.jmxremote.port=10103"
> fi
> {code}
> The variable names should be aligned for better user experience.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-17418) Use isEmpty instead of size() == 0 in hbase-rsgroup

2017-01-14 Thread Jan Hentschel (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-17418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Hentschel updated HBASE-17418:
--
Status: Patch Available  (was: In Progress)

> Use isEmpty instead of size() == 0 in hbase-rsgroup
> ---
>
> Key: HBASE-17418
> URL: https://issues.apache.org/jira/browse/HBASE-17418
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: HBASE-17418.master.001.patch
>
>
> Use {code:java}.isEmpty(){code} instead of {code:java}size() == 0{code} when 
> possible in the *hbase-rsgroup* module.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-17418) Use isEmpty instead of size() == 0 in hbase-rsgroup

2017-01-14 Thread Jan Hentschel (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-17418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Hentschel updated HBASE-17418:
--
Attachment: HBASE-17418.master.001.patch

> Use isEmpty instead of size() == 0 in hbase-rsgroup
> ---
>
> Key: HBASE-17418
> URL: https://issues.apache.org/jira/browse/HBASE-17418
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
> Attachments: HBASE-17418.master.001.patch
>
>
> Use {code:java}.isEmpty(){code} instead of {code:java}size() == 0{code} when 
> possible in the *hbase-rsgroup* module.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Assigned] (HBASE-17418) Use isEmpty instead of size() == 0 in hbase-rsgroup

2017-01-14 Thread Jan Hentschel (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-17418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Hentschel reassigned HBASE-17418:
-

Assignee: Jan Hentschel

> Use isEmpty instead of size() == 0 in hbase-rsgroup
> ---
>
> Key: HBASE-17418
> URL: https://issues.apache.org/jira/browse/HBASE-17418
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
>
> Use {code:java}.isEmpty(){code} instead of {code:java}size() == 0{code} when 
> possible in the *hbase-rsgroup* module.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Work started] (HBASE-17418) Use isEmpty instead of size() == 0 in hbase-rsgroup

2017-01-14 Thread Jan Hentschel (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-17418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on HBASE-17418 started by Jan Hentschel.
-
> Use isEmpty instead of size() == 0 in hbase-rsgroup
> ---
>
> Key: HBASE-17418
> URL: https://issues.apache.org/jira/browse/HBASE-17418
> Project: HBase
>  Issue Type: Sub-task
>Reporter: Jan Hentschel
>Assignee: Jan Hentschel
>Priority: Minor
>
> Use {code:java}.isEmpty(){code} instead of {code:java}size() == 0{code} when 
> possible in the *hbase-rsgroup* module.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Assigned] (HBASE-17469) Properly handle empty TableName in TablePermission#readFields and #write

2017-01-14 Thread Ted Yu (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-17469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ted Yu reassigned HBASE-17469:
--

Assignee: Manjunath Anand

> Properly handle empty TableName in TablePermission#readFields and #write
> 
>
> Key: HBASE-17469
> URL: https://issues.apache.org/jira/browse/HBASE-17469
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Manjunath Anand
>
> HBASE-17450 handles the empty table name in equals().
> This JIRA is to properly handle empty TableName in 
> TablePermission#readFields() and TablePermission#write() methods.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-17469) Properly handle empty TableName in TablePermission#readFields and #write

2017-01-14 Thread Ted Yu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-17469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822832#comment-15822832
 ] 

Ted Yu commented on HBASE-17469:


Please try to maintain backward compatibility:
TablePermission serialized by current code should be readable by new node

> Properly handle empty TableName in TablePermission#readFields and #write
> 
>
> Key: HBASE-17469
> URL: https://issues.apache.org/jira/browse/HBASE-17469
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>Assignee: Manjunath Anand
>
> HBASE-17450 handles the empty table name in equals().
> This JIRA is to properly handle empty TableName in 
> TablePermission#readFields() and TablePermission#write() methods.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (HBASE-17443) Move listReplicated/enableTableRep/disableTableRep methods from ReplicationAdmin to Admin

2017-01-14 Thread Guanghao Zhang (JIRA)

 [ 
https://issues.apache.org/jira/browse/HBASE-17443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Guanghao Zhang updated HBASE-17443:
---
Description: 
We have moved other replication requests to Admin and mark ReplicationAdmin as 
Deprecated, so listReplicated/enableTableRep/disableTableRep methods need move 
to Admin, too.

Review board: https://reviews.apache.org/r/55534/

  was:We have moved other replication requests to Admin and mark 
ReplicationAdmin as Deprecated, so 
listReplicated/enableTableRep/disableTableRep methods need move to Admin, too.


> Move listReplicated/enableTableRep/disableTableRep methods from 
> ReplicationAdmin to Admin
> -
>
> Key: HBASE-17443
> URL: https://issues.apache.org/jira/browse/HBASE-17443
> Project: HBase
>  Issue Type: Sub-task
>Affects Versions: 2.0.0
>Reporter: Guanghao Zhang
>Assignee: Guanghao Zhang
> Fix For: 2.0.0
>
> Attachments: HBASE-17443-v1.patch, HBASE-17443-v2.patch, 
> HBASE-17443-v2.patch, HBASE-17443-v3.patch
>
>
> We have moved other replication requests to Admin and mark ReplicationAdmin 
> as Deprecated, so listReplicated/enableTableRep/disableTableRep methods need 
> move to Admin, too.
> Review board: https://reviews.apache.org/r/55534/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-17469) Properly handle empty TableName in TablePermission#readFields and #write

2017-01-14 Thread Manjunath Anand (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-17469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822816#comment-15822816
 ] 

Manjunath Anand commented on HBASE-17469:
-

Hi [~yuzhih...@gmail.com] please let me know if I can assign this to myself and 
I can come up with patch and appropriate test case.

> Properly handle empty TableName in TablePermission#readFields and #write
> 
>
> Key: HBASE-17469
> URL: https://issues.apache.org/jira/browse/HBASE-17469
> Project: HBase
>  Issue Type: Bug
>Reporter: Ted Yu
>
> HBASE-17450 handles the empty table name in equals().
> This JIRA is to properly handle empty TableName in 
> TablePermission#readFields() and TablePermission#write() methods.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (HBASE-17437) Support specifying a WAL directory outside of the root directory

2017-01-14 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-17437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15822777#comment-15822777
 ] 

Hadoop QA commented on HBASE-17437:
---

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 14s 
{color} | {color:blue} Docker mode activated. {color} |
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m 
0s {color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m 0s 
{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m 
0s {color} | {color:green} The patch appears to include 21 new or modified test 
files. {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 29s 
{color} | {color:blue} Maven dependency ordering for branch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m 
1s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 0s 
{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 
58s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 
32s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 
34s {color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m 50s 
{color} | {color:green} master passed {color} |
| {color:blue}0{color} | {color:blue} mvndep {color} | {color:blue} 0m 10s 
{color} | {color:blue} Maven dependency ordering for patch {color} |
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 1m 
7s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 1m 0s 
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 1m 0s 
{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 0m 
58s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} mvneclipse {color} | {color:green} 0m 
31s {color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m 
0s {color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} xml {color} | {color:green} 0m 1s 
{color} | {color:green} The patch has no ill-formed XML file. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
25m 43s {color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7.1 2.7.2 2.7.3 or 3.0.0-alpha1. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m 
56s {color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} javadoc {color} | {color:red} 0m 26s 
{color} | {color:red} hbase-server generated 3 new + 1 unchanged - 0 fixed = 4 
total (was 1) {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 1m 42s 
{color} | {color:green} hbase-common in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 2m 22s 
{color} | {color:green} hbase-procedure in the patch passed. {color} |
| {color:green}+1{color} | {color:green} unit {color} | {color:green} 82m 29s 
{color} | {color:green} hbase-server in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m 
41s {color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 130m 53s {color} 
| {color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=1.12.3 Server=1.12.3 Image:yetus/hbase:8d52d23 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12847487/HBASE-17437.master.002.patch
 |
| JIRA Issue | HBASE-17437 |
| Optional Tests |  asflicense  javac  javadoc  unit  findbugs  hadoopcheck  
hbaseanti  checkstyle  compile  xml  |
| uname | Linux 59b19cf6ed90 3.13.0-95-generic #142-Ubuntu SMP Fri Aug 12 
17:00:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | master / 4cb09a4 |
| Default Java | 1.8.0_111 |
| findbugs | v3.0.0 |
| javadoc |