date:20140729


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

LinseyPang updated HBASE-11542:
---

Status: Open  (was: Patch Available)

 Unit Test  KeyStoreTestUtil.java compilation failure in IBM JDK 
 

 Key: HBASE-11542
 URL: https://issues.apache.org/jira/browse/HBASE-11542
 Project: HBase
  Issue Type: Improvement
  Components: build, test
Affects Versions: 0.99.0
 Environment: RHEL 6.3 ,IBM JDK 6
Reporter: LinseyPang
Priority: Minor
 Fix For: 2.0.0

 Attachments: HBASE_11542-1.patch, hbase_11542-v2.patch


 In trunk,  jira HBase-10336 added a utility test KeyStoreTestUtil.java, which 
 leverages the following sun classes:
    import sun.security.x509.AlgorithmId;
    import sun.security.x509.CertificateAlgorithmId;
   
 this cause hbase compiler failure if using IBM JDK,  
 There are similar classes like below in IBM jdk: 
 import com.ibm.security.x509.AlgorithmId;
 import com.ibm.security.x509.CertificateAlgorithmId; 
 This jira is to add handling of the x509 references. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HBASE-11542) Unit Test KeyStoreTestUtil.java compilation failure in IBM JDK


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

LinseyPang updated HBASE-11542:
---

Attachment: hbase11542-0.99-v3.patch

I created patch again and applied on local branch which is from master. It 
works on my eclipse project. Please have a test. Now submitting.

 Unit Test  KeyStoreTestUtil.java compilation failure in IBM JDK 
 

 Key: HBASE-11542
 URL: https://issues.apache.org/jira/browse/HBASE-11542
 Project: HBase
  Issue Type: Improvement
  Components: build, test
Affects Versions: 0.99.0
 Environment: RHEL 6.3 ,IBM JDK 6
Reporter: LinseyPang
Priority: Minor
 Fix For: 2.0.0

 Attachments: HBASE_11542-1.patch, hbase11542-0.99-v3.patch, 
 hbase_11542-v2.patch


 In trunk,  jira HBase-10336 added a utility test KeyStoreTestUtil.java, which 
 leverages the following sun classes:
    import sun.security.x509.AlgorithmId;
    import sun.security.x509.CertificateAlgorithmId;
   
 this cause hbase compiler failure if using IBM JDK,  
 There are similar classes like below in IBM jdk: 
 import com.ibm.security.x509.AlgorithmId;
 import com.ibm.security.x509.CertificateAlgorithmId; 
 This jira is to add handling of the x509 references. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HBASE-11542) Unit Test KeyStoreTestUtil.java compilation failure in IBM JDK


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

LinseyPang updated HBASE-11542:
---

Status: Patch Available  (was: Open)

 Unit Test  KeyStoreTestUtil.java compilation failure in IBM JDK 
 

 Key: HBASE-11542
 URL: https://issues.apache.org/jira/browse/HBASE-11542
 Project: HBase
  Issue Type: Improvement
  Components: build, test
Affects Versions: 0.99.0
 Environment: RHEL 6.3 ,IBM JDK 6
Reporter: LinseyPang
Priority: Minor
 Fix For: 2.0.0

 Attachments: HBASE_11542-1.patch, hbase11542-0.99-v3.patch, 
 hbase_11542-v2.patch


 In trunk,  jira HBase-10336 added a utility test KeyStoreTestUtil.java, which 
 leverages the following sun classes:
    import sun.security.x509.AlgorithmId;
    import sun.security.x509.CertificateAlgorithmId;
   
 this cause hbase compiler failure if using IBM JDK,  
 There are similar classes like below in IBM jdk: 
 import com.ibm.security.x509.AlgorithmId;
 import com.ibm.security.x509.CertificateAlgorithmId; 
 This jira is to add handling of the x509 references. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11542) Unit Test KeyStoreTestUtil.java compilation failure in IBM JDK


[ 
https://issues.apache.org/jira/browse/HBASE-11542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077577#comment-14077577
 ] 

LinseyPang commented on HBASE-11542:


Andrew, thanks . 

 Unit Test  KeyStoreTestUtil.java compilation failure in IBM JDK 
 

 Key: HBASE-11542
 URL: https://issues.apache.org/jira/browse/HBASE-11542
 Project: HBase
  Issue Type: Improvement
  Components: build, test
Affects Versions: 0.99.0
 Environment: RHEL 6.3 ,IBM JDK 6
Reporter: LinseyPang
Priority: Minor
 Fix For: 2.0.0

 Attachments: HBASE_11542-1.patch, hbase11542-0.99-v3.patch, 
 hbase_11542-v2.patch


 In trunk,  jira HBase-10336 added a utility test KeyStoreTestUtil.java, which 
 leverages the following sun classes:
    import sun.security.x509.AlgorithmId;
    import sun.security.x509.CertificateAlgorithmId;
   
 this cause hbase compiler failure if using IBM JDK,  
 There are similar classes like below in IBM jdk: 
 import com.ibm.security.x509.AlgorithmId;
 import com.ibm.security.x509.CertificateAlgorithmId; 
 This jira is to add handling of the x509 references. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11542) Unit Test KeyStoreTestUtil.java compilation failure in IBM JDK


[ 
https://issues.apache.org/jira/browse/HBASE-11542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077610#comment-14077610
 ] 

Hadoop QA commented on HBASE-11542:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12658389/hbase11542-0.99-v3.patch
  against trunk revision .
  ATTACHMENT ID: 12658389

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+1 tests included{color}.  The patch appears to include 21 new 
or modified tests.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

 {color:red}-1 core tests{color}.  The patch failed these unit tests:
 

 {color:red}-1 core zombie tests{color}.  There are 1 zombie test(s):   
at 
org.apache.hadoop.hbase.http.TestHttpServerLifecycle.testStoppedServerIsNotAlive(TestHttpServerLifecycle.java:115)

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10214//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10214//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10214//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10214//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10214//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10214//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10214//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10214//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10214//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10214//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10214//console

This message is automatically generated.

 Unit Test  KeyStoreTestUtil.java compilation failure in IBM JDK 
 

 Key: HBASE-11542
 URL: https://issues.apache.org/jira/browse/HBASE-11542
 Project: HBase
  Issue Type: Improvement
  Components: build, test
Affects Versions: 0.99.0
 Environment: RHEL 6.3 ,IBM JDK 6
Reporter: LinseyPang
Priority: Minor
 Fix For: 2.0.0

 Attachments: HBASE_11542-1.patch, hbase11542-0.99-v3.patch, 
 hbase_11542-v2.patch


 In trunk,  jira HBase-10336 added a utility test KeyStoreTestUtil.java, which 
 leverages the following sun classes:
    import sun.security.x509.AlgorithmId;
    import sun.security.x509.CertificateAlgorithmId;
   
 this cause hbase compiler failure if using IBM JDK,  
 There are similar classes like below in IBM jdk: 
 import com.ibm.security.x509.AlgorithmId;
 import com.ibm.security.x509.CertificateAlgorithmId; 
 This jira is to add handling of the x509 references. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11542) Unit Test KeyStoreTestUtil.java compilation failure in IBM JDK


[ 
https://issues.apache.org/jira/browse/HBASE-11542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077619#comment-14077619
 ] 

LinseyPang commented on HBASE-11542:


Can give some advices for this time's failure ? thanks a lot. 

 Unit Test  KeyStoreTestUtil.java compilation failure in IBM JDK 
 

 Key: HBASE-11542
 URL: https://issues.apache.org/jira/browse/HBASE-11542
 Project: HBase
  Issue Type: Improvement
  Components: build, test
Affects Versions: 0.99.0
 Environment: RHEL 6.3 ,IBM JDK 6
Reporter: LinseyPang
Priority: Minor
 Fix For: 2.0.0

 Attachments: HBASE_11542-1.patch, hbase11542-0.99-v3.patch, 
 hbase_11542-v2.patch


 In trunk,  jira HBase-10336 added a utility test KeyStoreTestUtil.java, which 
 leverages the following sun classes:
    import sun.security.x509.AlgorithmId;
    import sun.security.x509.CertificateAlgorithmId;
   
 this cause hbase compiler failure if using IBM JDK,  
 There are similar classes like below in IBM jdk: 
 import com.ibm.security.x509.AlgorithmId;
 import com.ibm.security.x509.CertificateAlgorithmId; 
 This jira is to add handling of the x509 references. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11425) Cell/DBB end-to-end on the read-path

2014-07-29 Thread Anoop Sam John (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-11425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077656#comment-14077656
 ] 

Anoop Sam John commented on HBASE-11425:


Testing with a 2 million Cells with single cell per row.
Writing all cells to a BB/DBB and trying a seek with to last kv. (To make 
compare across all cells in BB/DBB)
Seek code is like what we have in ScannerV3#blockSeek

with RK length 17 bytes (1st 13 bytes are same) Getting almost same  result.
With RK length 117 bytes (1st 113 bytes are same) the DBB based read is ~3% 
degrade.


 Cell/DBB end-to-end on the read-path
 

 Key: HBASE-11425
 URL: https://issues.apache.org/jira/browse/HBASE-11425
 Project: HBase
  Issue Type: Umbrella
  Components: regionserver, Scanners
Affects Versions: 0.99.0
Reporter: Anoop Sam John
Assignee: Anoop Sam John

 Umbrella jira to make sure we can have blocks cached in offheap backed cache. 
 In the entire read path, we can refer to this offheap buffer and avoid onheap 
 copying.
 The high level items I can identify as of now are
 1. Avoid the array() call on BB in read path.. (This is there in many 
 classes. We can handle class by class)
 2. Support Buffer based getter APIs in cell.  In read path we will create a 
 new Cell with backed by BB. Will need in CellComparator, Filter (like SCVF), 
 CPs etc.
 3. Avoid KeyValue.ensureKeyValue() calls in read path - This make byte copy.
 4. Remove all CP hooks (which are already deprecated) which deal with KVs.  
 (In read path)
 Will add subtasks under this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HBASE-4744) Remove @Ignore for testLogRollAfterSplitStart

2014-07-29 Thread Sean Busbey (JIRA)


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

Sean Busbey updated HBASE-4744:
---

Labels: newbie  (was: )

 Remove @Ignore for testLogRollAfterSplitStart
 -

 Key: HBASE-4744
 URL: https://issues.apache.org/jira/browse/HBASE-4744
 Project: HBase
  Issue Type: Test
Affects Versions: 0.94.0
Reporter: Nicolas Spiegelberg
Priority: Critical
  Labels: newbie

 We fixed a data loss bug in HBASE-2312 by adding non-recursive creates to 
 HDFS.  Although a number of HDFS versions have this fix, the official HDFS 
 0.20.205 branch currently doesn't, so we needed to mark the test as ignored.  
 Please revisit before the RC of 0.94, which should have 0.20.205.1 or later  
 the necessary HDFS patches.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-6763) fs.default.name has been moved to fs.defaultFS we did not migrate all of the code.

2014-07-29 Thread Sean Busbey (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1400#comment-1400
 ] 

Sean Busbey commented on HBASE-6763:


All references to fs.default.name have been removed in master. It looks like 
0.98 attempts to set both properties, but there are a few places that only set 
one or the other.

Fine to close? Or would folks like a patch against 0.98 to make our use of both 
consistent?

 fs.default.name has been moved to fs.defaultFS we did not migrate all of the 
 code.
 --

 Key: HBASE-6763
 URL: https://issues.apache.org/jira/browse/HBASE-6763
 Project: HBase
  Issue Type: Bug
  Components: master
Affects Versions: 0.95.2
Reporter: Kevin Odell
  Labels: newbie

 We are getting warning messages:
 WARN org.apache.hadoop.conf.Configuration: fs.default.name is deprecated. 
 Instead, use fs.defaultFS
 This occurs even when the core-site.xml is properly set up.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11425) Cell/DBB end-to-end on the read-path


[ 
https://issues.apache.org/jira/browse/HBASE-11425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077868#comment-14077868
 ] 

Andrew Purtell commented on HBASE-11425:


This is with BB or BR? How about 1kb RKs?

 Cell/DBB end-to-end on the read-path
 

 Key: HBASE-11425
 URL: https://issues.apache.org/jira/browse/HBASE-11425
 Project: HBase
  Issue Type: Umbrella
  Components: regionserver, Scanners
Affects Versions: 0.99.0
Reporter: Anoop Sam John
Assignee: Anoop Sam John

 Umbrella jira to make sure we can have blocks cached in offheap backed cache. 
 In the entire read path, we can refer to this offheap buffer and avoid onheap 
 copying.
 The high level items I can identify as of now are
 1. Avoid the array() call on BB in read path.. (This is there in many 
 classes. We can handle class by class)
 2. Support Buffer based getter APIs in cell.  In read path we will create a 
 new Cell with backed by BB. Will need in CellComparator, Filter (like SCVF), 
 CPs etc.
 3. Avoid KeyValue.ensureKeyValue() calls in read path - This make byte copy.
 4. Remove all CP hooks (which are already deprecated) which deal with KVs.  
 (In read path)
 Will add subtasks under this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11425) Cell/DBB end-to-end on the read-path

2014-07-29 Thread Anoop Sam John (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-11425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077898#comment-14077898
 ] 

Anoop Sam John commented on HBASE-11425:


BB only.  And not the actual read perf number. Just the seek part and so reads 
from BB vs DBB
bq.How about 1kb RKs?
Will test more cases.

 Cell/DBB end-to-end on the read-path
 

 Key: HBASE-11425
 URL: https://issues.apache.org/jira/browse/HBASE-11425
 Project: HBase
  Issue Type: Umbrella
  Components: regionserver, Scanners
Affects Versions: 0.99.0
Reporter: Anoop Sam John
Assignee: Anoop Sam John

 Umbrella jira to make sure we can have blocks cached in offheap backed cache. 
 In the entire read path, we can refer to this offheap buffer and avoid onheap 
 copying.
 The high level items I can identify as of now are
 1. Avoid the array() call on BB in read path.. (This is there in many 
 classes. We can handle class by class)
 2. Support Buffer based getter APIs in cell.  In read path we will create a 
 new Cell with backed by BB. Will need in CellComparator, Filter (like SCVF), 
 CPs etc.
 3. Avoid KeyValue.ensureKeyValue() calls in read path - This make byte copy.
 4. Remove all CP hooks (which are already deprecated) which deal with KVs.  
 (In read path)
 Will add subtasks under this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HBASE-11540) Document HBASE-11474


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

Jimmy Xiang updated HBASE-11540:


   Resolution: Fixed
Fix Version/s: 2.0.0
   1.0.0
 Hadoop Flags: Reviewed
   Status: Resolved  (was: Patch Available)

Thanks Misty a lot for the patch. Integrated into branch 1 and master.

 Document HBASE-11474
 

 Key: HBASE-11540
 URL: https://issues.apache.org/jira/browse/HBASE-11540
 Project: HBase
  Issue Type: Bug
  Components: documentation
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
Priority: Critical
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-11540-1.patch, HBASE-11540.patch






--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11425) Cell/DBB end-to-end on the read-path


[ 
https://issues.apache.org/jira/browse/HBASE-11425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077940#comment-14077940
 ] 

Andrew Purtell commented on HBASE-11425:


Does it make a difference if using the BR API instead?

 Cell/DBB end-to-end on the read-path
 

 Key: HBASE-11425
 URL: https://issues.apache.org/jira/browse/HBASE-11425
 Project: HBase
  Issue Type: Umbrella
  Components: regionserver, Scanners
Affects Versions: 0.99.0
Reporter: Anoop Sam John
Assignee: Anoop Sam John

 Umbrella jira to make sure we can have blocks cached in offheap backed cache. 
 In the entire read path, we can refer to this offheap buffer and avoid onheap 
 copying.
 The high level items I can identify as of now are
 1. Avoid the array() call on BB in read path.. (This is there in many 
 classes. We can handle class by class)
 2. Support Buffer based getter APIs in cell.  In read path we will create a 
 new Cell with backed by BB. Will need in CellComparator, Filter (like SCVF), 
 CPs etc.
 3. Avoid KeyValue.ensureKeyValue() calls in read path - This make byte copy.
 4. Remove all CP hooks (which are already deprecated) which deal with KVs.  
 (In read path)
 Will add subtasks under this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11542) Unit Test KeyStoreTestUtil.java compilation failure in IBM JDK

2014-07-29 Thread Ted Yu (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-11542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077957#comment-14077957
 ] 

Ted Yu commented on HBASE-11542:


I searched in console log of the QA run for TestHttpServerLifecycle - this test 
did seem to hang.

 Unit Test  KeyStoreTestUtil.java compilation failure in IBM JDK 
 

 Key: HBASE-11542
 URL: https://issues.apache.org/jira/browse/HBASE-11542
 Project: HBase
  Issue Type: Improvement
  Components: build, test
Affects Versions: 0.99.0
 Environment: RHEL 6.3 ,IBM JDK 6
Reporter: LinseyPang
Priority: Minor
 Fix For: 2.0.0

 Attachments: HBASE_11542-1.patch, hbase11542-0.99-v3.patch, 
 hbase_11542-v2.patch


 In trunk,  jira HBase-10336 added a utility test KeyStoreTestUtil.java, which 
 leverages the following sun classes:
    import sun.security.x509.AlgorithmId;
    import sun.security.x509.CertificateAlgorithmId;
   
 this cause hbase compiler failure if using IBM JDK,  
 There are similar classes like below in IBM jdk: 
 import com.ibm.security.x509.AlgorithmId;
 import com.ibm.security.x509.CertificateAlgorithmId; 
 This jira is to add handling of the x509 references. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11425) Cell/DBB end-to-end on the read-path


[ 
https://issues.apache.org/jira/browse/HBASE-11425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077991#comment-14077991
 ] 

stack commented on HBASE-11425:
---

Nice [~anoop.hbase] Mind posting your little test tool so can run local?

 Cell/DBB end-to-end on the read-path
 

 Key: HBASE-11425
 URL: https://issues.apache.org/jira/browse/HBASE-11425
 Project: HBase
  Issue Type: Umbrella
  Components: regionserver, Scanners
Affects Versions: 0.99.0
Reporter: Anoop Sam John
Assignee: Anoop Sam John

 Umbrella jira to make sure we can have blocks cached in offheap backed cache. 
 In the entire read path, we can refer to this offheap buffer and avoid onheap 
 copying.
 The high level items I can identify as of now are
 1. Avoid the array() call on BB in read path.. (This is there in many 
 classes. We can handle class by class)
 2. Support Buffer based getter APIs in cell.  In read path we will create a 
 new Cell with backed by BB. Will need in CellComparator, Filter (like SCVF), 
 CPs etc.
 3. Avoid KeyValue.ensureKeyValue() calls in read path - This make byte copy.
 4. Remove all CP hooks (which are already deprecated) which deal with KVs.  
 (In read path)
 Will add subtasks under this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11474) [Thrift2] support authentication/impersonation


[ 
https://issues.apache.org/jira/browse/HBASE-11474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078003#comment-14078003
 ] 

Hudson commented on HBASE-11474:


FAILURE: Integrated in HBase-TRUNK #5351 (See 
[https://builds.apache.org/job/HBase-TRUNK/5351/])
HBASE-11540 Document HBASE-11474 (Misty Stanley-Jones) (jxiang: rev 
9cc2b0ae9d8f08e01cc703447994368596e9874a)
* src/main/docbkx/thrift_filter_language.xml
* src/main/docbkx/security.xml


 [Thrift2] support authentication/impersonation
 --

 Key: HBASE-11474
 URL: https://issues.apache.org/jira/browse/HBASE-11474
 Project: HBase
  Issue Type: Improvement
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Fix For: 0.99.0, 0.98.4, 2.0.0

 Attachments: hbase-11474.patch, hbase-11474_1.patch


 This is to do the same as HBASE-11349 for Thrift2.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11540) Document HBASE-11474


[ 
https://issues.apache.org/jira/browse/HBASE-11540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078004#comment-14078004
 ] 

Hudson commented on HBASE-11540:


FAILURE: Integrated in HBase-TRUNK #5351 (See 
[https://builds.apache.org/job/HBase-TRUNK/5351/])
HBASE-11540 Document HBASE-11474 (Misty Stanley-Jones) (jxiang: rev 
9cc2b0ae9d8f08e01cc703447994368596e9874a)
* src/main/docbkx/thrift_filter_language.xml
* src/main/docbkx/security.xml


 Document HBASE-11474
 

 Key: HBASE-11540
 URL: https://issues.apache.org/jira/browse/HBASE-11540
 Project: HBase
  Issue Type: Bug
  Components: documentation
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
Priority: Critical
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-11540-1.patch, HBASE-11540.patch






--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11316) Expand info about compactions beyond HBASE-11120


[ 
https://issues.apache.org/jira/browse/HBASE-11316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078013#comment-14078013
 ] 

stack commented on HBASE-11316:
---

Interesting.  The test failures are legit:

org.apache.hadoop.hbase.regionserver.compactions.TestStripeCompactionPolicy
org.apache.hadoop.hbase.regionserver.TestDefaultCompactSelection

The hbase-default additions seem to break above tests.  Let me isolate which 
changes are responsible for the break.

 Expand info about compactions beyond HBASE-11120
 

 Key: HBASE-11316
 URL: https://issues.apache.org/jira/browse/HBASE-11316
 Project: HBase
  Issue Type: Bug
  Components: Compaction, documentation
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
 Fix For: 2.0.0

 Attachments: HBASE-11316-1.patch, HBASE-11316-2.patch, 
 HBASE-11316-3.patch, HBASE-11316-4.patch, HBASE-11316-5.patch, 
 HBASE-11316-6-rebased-v2.patch, HBASE-11316-6-rebased.patch, 
 HBASE-11316-6.patch, HBASE-11316-7.patch, HBASE-11316-8.patch, 
 HBASE-11316-9.patch, HBASE-11316.patch, ch9_compactions.pdf


 Round 2 - expand info about the algorithms, talk about stripe compaction, and 
 talk more about configuration. Hopefully find some rules of thumb.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-6763) fs.default.name has been moved to fs.defaultFS we did not migrate all of the code.


[ 
https://issues.apache.org/jira/browse/HBASE-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078019#comment-14078019
 ] 

stack commented on HBASE-6763:
--

Getting rid of WARNs would be a nice-to-have but if you want to work on 
something more pressing, that'd be cool too Mr. [~busbey]

 fs.default.name has been moved to fs.defaultFS we did not migrate all of the 
 code.
 --

 Key: HBASE-6763
 URL: https://issues.apache.org/jira/browse/HBASE-6763
 Project: HBase
  Issue Type: Bug
  Components: master
Affects Versions: 0.95.2
Reporter: Kevin Odell
  Labels: newbie

 We are getting warning messages:
 WARN org.apache.hadoop.conf.Configuration: fs.default.name is deprecated. 
 Instead, use fs.defaultFS
 This occurs even when the core-site.xml is properly set up.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-9741) Remove hbase.regions.slop from hbase-default.xml

2014-07-29 Thread Esteban Gutierrez (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078049#comment-14078049
 ] 

Esteban Gutierrez commented on HBASE-9741:
--

Why not rename the {{hbase.regions.slop}} initially to 
{{hbase.regions.balancer.base.slop}} and add a new property for the 
StochasticLoadBalancer {{hbase.regions.balancer.stochastic.slop}}. Then we can 
deprecate gracefully {{hbase.regions.slop}} with a warning and still support 
the property for a while.

 Remove hbase.regions.slop from hbase-default.xml
 

 Key: HBASE-9741
 URL: https://issues.apache.org/jira/browse/HBASE-9741
 Project: HBase
  Issue Type: Bug
Reporter: Elliott Clark
  Labels: noob
 Attachments: HBASE-9741-v0.patch, HBASE-9741-v1.patch


 Different balancers have different slop default values.  We should remove 
 hbase.regions.slop from hbase-default.xml



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HBASE-11558) Caching set on Scan object gets lost when using TableMapReduceUtil in 0.95+

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

Andrew Purtell updated HBASE-11558:
---

Status: Open (was: Patch Available)

Caching set on Scan object gets lost when using TableMapReduceUtil in 0.95+
---

Key: HBASE-11558
URL: https://issues.apache.org/jira/browse/HBASE-11558
Project: HBase
Issue Type: Bug
Components: mapreduce, Scanners
Reporter: Ishan Chhabra
Assignee: Ishan Chhabra
Fix For: 0.99.0, 0.96.3, 0.98.5, 2.0.0

Attachments: HBASE_11558-0.96.patch, HBASE_11558-0.96_v2.patch,
HBASE_11558-0.98.patch, HBASE_11558-0.98_v2.patch, HBASE_11558.patch,
HBASE_11558_v2.patch

0.94 and before, if one sets caching on the Scan object in the Job by calling
scan.setCaching(int) and passes it to TableMapReduceUtil, it is correctly
read and used by the mappers during a mapreduce job. This is because
Scan.write respects and serializes caching, which is used internally by
TableMapReduceUtil to serialize and transfer the scan object to the mappers.
0.95+, after the move to protobuf, ProtobufUtil.toScan does not respect
caching anymore as ClientProtos.Scan does not have the field caching. Caching
is passed via the ScanRequest object to the server and so is not needed in
the Scan object. However, this breaks application code that relies on the
earlier behavior. This will lead to sudden degradation in Scan performance
0.96+ for users relying on the old behavior.
There are 2 options here:
1. Add caching to Scan object, adding an extra int to the payload for the
Scan object which is really not needed in the general case.
2. Document and preach that TableMapReduceUtil.setScannerCaching must be
called by the client.

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HBASE-11558) Caching set on Scan object gets lost when using TableMapReduceUtil in 0.95+

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

Andrew Purtell updated HBASE-11558:
---

Attachment: HBASE_11558_v2.patch

Attach trunk patch again to be most current

Caching set on Scan object gets lost when using TableMapReduceUtil in 0.95+
---

Attachments: HBASE_11558-0.96.patch, HBASE_11558-0.96_v2.patch,
HBASE_11558-0.98.patch, HBASE_11558-0.98_v2.patch, HBASE_11558.patch,
HBASE_11558_v2.patch, HBASE_11558_v2.patch

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HBASE-11558) Caching set on Scan object gets lost when using TableMapReduceUtil in 0.95+

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

Andrew Purtell updated HBASE-11558:
---

Status: Patch Available (was: Open)

Caching set on Scan object gets lost when using TableMapReduceUtil in 0.95+
---

Attachments: HBASE_11558-0.96.patch, HBASE_11558-0.96_v2.patch,
HBASE_11558-0.98.patch, HBASE_11558-0.98_v2.patch, HBASE_11558.patch,
HBASE_11558_v2.patch, HBASE_11558_v2.patch

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HBASE-11316) Expand info about compactions beyond HBASE-11120


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

stack updated HBASE-11316:
--

Attachment: addendum.txt

Addendum. The two failing tests don't like the setting of explicit new default 
in hbase-default.xml of hbase.hstore.compaction.min.size so just unset this 
value so these tests pass again.

 Expand info about compactions beyond HBASE-11120
 

 Key: HBASE-11316
 URL: https://issues.apache.org/jira/browse/HBASE-11316
 Project: HBase
  Issue Type: Bug
  Components: Compaction, documentation
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
 Fix For: 2.0.0

 Attachments: HBASE-11316-1.patch, HBASE-11316-2.patch, 
 HBASE-11316-3.patch, HBASE-11316-4.patch, HBASE-11316-5.patch, 
 HBASE-11316-6-rebased-v2.patch, HBASE-11316-6-rebased.patch, 
 HBASE-11316-6.patch, HBASE-11316-7.patch, HBASE-11316-8.patch, 
 HBASE-11316-9.patch, HBASE-11316.patch, addendum.txt, ch9_compactions.pdf


 Round 2 - expand info about the algorithms, talk about stripe compaction, and 
 talk more about configuration. Hopefully find some rules of thumb.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11316) Expand info about compactions beyond HBASE-11120

2014-07-29 Thread Jean-Daniel Cryans (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-11316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078104#comment-14078104
 ] 

Jean-Daniel Cryans commented on HBASE-11316:


+1, thanks for looking at this Stack and sorry I overlooked those failing tests.

 Expand info about compactions beyond HBASE-11120
 

 Key: HBASE-11316
 URL: https://issues.apache.org/jira/browse/HBASE-11316
 Project: HBase
  Issue Type: Bug
  Components: Compaction, documentation
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
 Fix For: 2.0.0

 Attachments: HBASE-11316-1.patch, HBASE-11316-2.patch, 
 HBASE-11316-3.patch, HBASE-11316-4.patch, HBASE-11316-5.patch, 
 HBASE-11316-6-rebased-v2.patch, HBASE-11316-6-rebased.patch, 
 HBASE-11316-6.patch, HBASE-11316-7.patch, HBASE-11316-8.patch, 
 HBASE-11316-9.patch, HBASE-11316.patch, addendum.txt, ch9_compactions.pdf


 Round 2 - expand info about the algorithms, talk about stripe compaction, and 
 talk more about configuration. Hopefully find some rules of thumb.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11558) Caching set on Scan object gets lost when using TableMapReduceUtil in 0.95+

[
https://issues.apache.org/jira/browse/HBASE-11558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078141#comment-14078141
]

Hadoop QA commented on HBASE-11558:
---

{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12658453/HBASE_11558_v2.patch
against trunk revision .
ATTACHMENT ID: 12658453

{color:green}+1 @author{color}. The patch does not contain any @author
tags.

{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.

{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.

{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.

{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.

{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ \022\024\n\014more_results\030\003
\001(\010\022\013\n\003ttl\030\004 \001(\r\022\030\n\007r +
+ new java.lang.String[] { Column, Attribute, StartRow,
StopRow, Filter, TimeRange, MaxVersions, CacheBlocks, BatchSize,
MaxResultSize, StoreLimit, StoreOffset, LoadColumnFamiliesOnDemand,
Small, Reversed, Consistency, Caching, });

{color:green}+1 site{color}. The mvn site goal succeeds with this patch.

{color:red}-1 core tests{color}. The patch failed these unit tests:

org.apache.hadoop.hbase.regionserver.compactions.TestStripeCompactionPolicy

org.apache.hadoop.hbase.regionserver.TestDefaultCompactSelection

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/10215//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10215//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10215//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10215//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10215//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10215//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10215//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10215//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10215//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10215//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/10215//console

This message is automatically generated.

Caching set on Scan object gets lost when using TableMapReduceUtil in 0.95+
---

Attachments: HBASE_11558-0.96.patch, HBASE_11558-0.96_v2.patch,
HBASE_11558-0.98.patch, HBASE_11558-0.98_v2.patch, HBASE_11558.patch,
HBASE_11558_v2.patch, HBASE_11558_v2.patch

[jira] [Commented] (HBASE-9741) Remove hbase.regions.slop from hbase-default.xml

2014-07-29 Thread Elliott Clark (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078153#comment-14078153
 ] 

Elliott Clark commented on HBASE-9741:
--

Because the stochastic balancer doesn't really use the slop in the same way.  
It computes costs, so slop isn't really used to determine when a balance plan 
is good.

 Remove hbase.regions.slop from hbase-default.xml
 

 Key: HBASE-9741
 URL: https://issues.apache.org/jira/browse/HBASE-9741
 Project: HBase
  Issue Type: Bug
Reporter: Elliott Clark
  Labels: noob
 Attachments: HBASE-9741-v0.patch, HBASE-9741-v1.patch


 Different balancers have different slop default values.  We should remove 
 hbase.regions.slop from hbase-default.xml



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-9741) Remove hbase.regions.slop from hbase-default.xml

2014-07-29 Thread Esteban Gutierrez (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-9741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078156#comment-14078156
 ] 

Esteban Gutierrez commented on HBASE-9741:
--

[~eclark] then it might be better to rename {{hbase.regions.slop}} the the 
StochasticLoadBalancer to {{hbase.regions.stochastic.load.balancer.cost}} and 
do not rename {{hbase.regions.slop}} does it sounds good?

 Remove hbase.regions.slop from hbase-default.xml
 

 Key: HBASE-9741
 URL: https://issues.apache.org/jira/browse/HBASE-9741
 Project: HBase
  Issue Type: Bug
Reporter: Elliott Clark
  Labels: noob
 Attachments: HBASE-9741-v0.patch, HBASE-9741-v1.patch


 Different balancers have different slop default values.  We should remove 
 hbase.regions.slop from hbase-default.xml



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (HBASE-11608) Add synchronous split

Jerry He created HBASE-11608:


 Summary: Add synchronous split
 Key: HBASE-11608
 URL: https://issues.apache.org/jira/browse/HBASE-11608
 Project: HBase
  Issue Type: New Feature
  Components: Admin
Affects Versions: 0.99.0, 0.98.5
Reporter: Jerry He


Users have been asking for this. We have an internal requirement for this as 
well.
The goal is a provide a Admin API (and shell command) so that users can request 
to split a region or table and get the split completion result synchronously.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11608) Add synchronous split


[ 
https://issues.apache.org/jira/browse/HBASE-11608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078179#comment-14078179
 ] 

Jerry He commented on HBASE-11608:
--

Linked to an old issue that raised this request.

 Add synchronous split
 -

 Key: HBASE-11608
 URL: https://issues.apache.org/jira/browse/HBASE-11608
 Project: HBase
  Issue Type: New Feature
  Components: Admin
Affects Versions: 0.99.0, 0.98.5
Reporter: Jerry He

 Users have been asking for this. We have an internal requirement for this as 
 well.
 The goal is a provide a Admin API (and shell command) so that users can 
 request to split a region or table and get the split completion result 
 synchronously.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11608) Add synchronous split

[
https://issues.apache.org/jira/browse/HBASE-11608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078215#comment-14078215
]

Jerry He commented on HBASE-11608:
--

Carry over the design comment from HBase-2949 so we will continue the
discussion here.

+Current implementation on the client side+

In HBaseAdmin.split(),
1. Input is a region name
1a. If a split key is given, we will send a split request to the region server
hosting the region containing the key. Asynchronous operation.
2b. If no split key, we will send a split request to the region server hosting
the region to split based split policy. Asynchronous operation.
2. Input is a table name
1a. If a split key is given, we will send a split request to the region server
hosting the region containing the key. Asynchronous operation.
2b. If no split key, we will send split requests in a loop to (region, rs) pair
for all the regions of the table to split based split policy. Asynchronous
operation.

+Current implementation on the region server side+

HRegionServer - RSRpcServices.splitRegion() -
compactSplitThread.requestSplit() -- CompactSplitThread.splits.execute(new
SplitRequest())
CompactSplitThread.splits is a ThreadPoolExecutor.
SplitRequest is a Runnable that does all the slit work.

+Goal+

Backward compatible, no impact on existing system triggered split, minimum
overall impact, more??

+Proposed change on the region server side+

Provide a synchronous
compactSplitThread.requestSplitSynchronous() --
CompactSplitThread.splits.submit(new SplitRequest()) and wait for 'future'
completion.
SplitRequest currently is a Runnable.
Possibly change it to CallableVoid so that we can propagate up any exceptions
during split operation
as we want to get notified any errors/exceptions synchronously as well.
HRegionServer - RSRpcServices.splitRegionSynchronous() will use the new
requestSplitSynchronous().

+On the HBaseAdmin side+

If we go synchronous in HBaseAdmin.split(), one use case scenario will become
less efficient. i.e. the 2.b case from above:
bq. 2b. If no split key, we will send split requests in a loop to (region, rs)
pair for all the regions of the table to split based split policy.
Because in this case, each (region, rs) pair will be requested serially and
synchronously.
We'll provide a HBaseAdmin.splitSynchronous() and keep the current asynchronous
HBaseAdmin.split().
Users are kept aware of the choices they have.
In the future HBaseAdmin.splitSynchronous() can be improved (e.g. using Global
procedure in split regions in parallel).

This is my initial thinking.
Your comments please, if this is doable, if there is any concern, if I miss or
misunderstand anything. I am sure I do :-)

Add synchronous split
-

Key: HBASE-11608
URL: https://issues.apache.org/jira/browse/HBASE-11608
Project: HBase
Issue Type: New Feature
Components: Admin
Affects Versions: 0.99.0, 0.98.5
Reporter: Jerry He

Users have been asking for this. We have an internal requirement for this as
well.
The goal is a provide a Admin API (and shell command) so that users can
request to split a region or table and get the split completion result
synchronously.

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HBASE-11609) LoadIncrementalHFiles fails if the namespace is specified


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

Matteo Bertozzi updated HBASE-11609:


Attachment: HBASE-11609-v0.patch

 LoadIncrementalHFiles fails if the namespace is specified
 -

 Key: HBASE-11609
 URL: https://issues.apache.org/jira/browse/HBASE-11609
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 1.0.0, 0.98.4, 2.0.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
 Fix For: 1.0.0, 0.98.5, 2.0.0

 Attachments: HBASE-11609-v0.patch


 from Jianshi Huang on the user list
 trying to bulk load a table in a namespace, like:
 $ hbase org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles test/ 
 foo:testtb
 we get an exception
 {code}
 2014-07-29 19:59:53,373 ERROR [main] mapreduce.LoadIncrementalHFiles: 
 Unexpected execution exception during splitting
 java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: 
 java.net.URISyntaxException: Relative path in absolute URI: 
 foo:testtb,1.bottom
 at java.util.concurrent.FutureTask.report(FutureTask.java:122)
 at java.util.concurrent.FutureTask.get(FutureTask.java:188)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.groupOrSplitPhase(LoadIncrementalHFiles.java:449)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.doBulkLoad(LoadIncrementalHFiles.java:304)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.run(LoadIncrementalHFiles.java:899)
 at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
 at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
 {code}
 The problem is related to the ':' symbol going to the file path. the simple 
 fix is to replace the current LoadIncrementalHFiles.getUniqueName()



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (HBASE-11609) LoadIncrementalHFiles fails if the namespace is specified

Matteo Bertozzi created HBASE-11609:
---

 Summary: LoadIncrementalHFiles fails if the namespace is specified
 Key: HBASE-11609
 URL: https://issues.apache.org/jira/browse/HBASE-11609
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 0.98.4, 1.0.0, 2.0.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
 Fix For: 1.0.0, 0.98.5, 2.0.0
 Attachments: HBASE-11609-v0.patch

from Jianshi Huang on the user list
trying to bulk load a table in a namespace, like:
$ hbase org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles test/ foo:testtb

we get an exception
{code}
2014-07-29 19:59:53,373 ERROR [main] mapreduce.LoadIncrementalHFiles: 
Unexpected execution exception during splitting
java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: 
java.net.URISyntaxException: Relative path in absolute URI: foo:testtb,1.bottom
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:188)
at 
org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.groupOrSplitPhase(LoadIncrementalHFiles.java:449)
at 
org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.doBulkLoad(LoadIncrementalHFiles.java:304)
at 
org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.run(LoadIncrementalHFiles.java:899)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
{code}

The problem is related to the ':' symbol going to the file path. the simple fix 
is to replace the current LoadIncrementalHFiles.getUniqueName()



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HBASE-11609) LoadIncrementalHFiles fails if the namespace is specified


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

Matteo Bertozzi updated HBASE-11609:


Status: Patch Available  (was: Open)

 LoadIncrementalHFiles fails if the namespace is specified
 -

 Key: HBASE-11609
 URL: https://issues.apache.org/jira/browse/HBASE-11609
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 0.98.4, 1.0.0, 2.0.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
 Fix For: 1.0.0, 0.98.5, 2.0.0

 Attachments: HBASE-11609-v0.patch


 from Jianshi Huang on the user list
 trying to bulk load a table in a namespace, like:
 $ hbase org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles test/ 
 foo:testtb
 we get an exception
 {code}
 2014-07-29 19:59:53,373 ERROR [main] mapreduce.LoadIncrementalHFiles: 
 Unexpected execution exception during splitting
 java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: 
 java.net.URISyntaxException: Relative path in absolute URI: 
 foo:testtb,1.bottom
 at java.util.concurrent.FutureTask.report(FutureTask.java:122)
 at java.util.concurrent.FutureTask.get(FutureTask.java:188)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.groupOrSplitPhase(LoadIncrementalHFiles.java:449)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.doBulkLoad(LoadIncrementalHFiles.java:304)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.run(LoadIncrementalHFiles.java:899)
 at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
 at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
 {code}
 The problem is related to the ':' symbol going to the file path. the simple 
 fix is to replace the current LoadIncrementalHFiles.getUniqueName()



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11609) LoadIncrementalHFiles fails if the namespace is specified


[ 
https://issues.apache.org/jira/browse/HBASE-11609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078273#comment-14078273
 ] 

Hadoop QA commented on HBASE-11609:
---

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12658468/HBASE-11609-v0.patch
  against trunk revision .
  ATTACHMENT ID: 12658468

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn site goal succeeds with this patch.

 {color:red}-1 core tests{color}.  The patch failed these unit tests:
   
org.apache.hadoop.hbase.regionserver.compactions.TestStripeCompactionPolicy
  
org.apache.hadoop.hbase.regionserver.TestDefaultCompactSelection

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10216//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10216//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10216//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10216//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10216//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10216//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10216//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10216//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10216//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10216//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10216//console

This message is automatically generated.

 LoadIncrementalHFiles fails if the namespace is specified
 -

 Key: HBASE-11609
 URL: https://issues.apache.org/jira/browse/HBASE-11609
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 1.0.0, 0.98.4, 2.0.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
 Fix For: 1.0.0, 0.98.5, 2.0.0

 Attachments: HBASE-11609-v0.patch


 from Jianshi Huang on the user list
 trying to bulk load a table in a namespace, like:
 $ hbase org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles test/ 
 foo:testtb
 we get an exception
 {code}
 2014-07-29 19:59:53,373 ERROR [main] mapreduce.LoadIncrementalHFiles: 
 Unexpected execution exception during splitting
 java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: 
 java.net.URISyntaxException: Relative path in absolute URI: 
 foo:testtb,1.bottom
 at java.util.concurrent.FutureTask.report(FutureTask.java:122)
 at java.util.concurrent.FutureTask.get(FutureTask.java:188)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.groupOrSplitPhase(LoadIncrementalHFiles.java:449)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.doBulkLoad(LoadIncrementalHFiles.java:304)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.run(LoadIncrementalHFiles.java:899)
 at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
 at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
 {code}
 The

[jira] [Commented] (HBASE-11608) Add synchronous split

2014-07-29 Thread Nick Dimiduk (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-11608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078343#comment-14078343
 ] 

Nick Dimiduk commented on HBASE-11608:
--

Nice feature [~jinghe].

How will your future approach handle intermittent connectivity issues between 
client and RS? Have you looked at HBASE-5487 ?

 Add synchronous split
 -

 Key: HBASE-11608
 URL: https://issues.apache.org/jira/browse/HBASE-11608
 Project: HBase
  Issue Type: New Feature
  Components: Admin
Affects Versions: 0.99.0, 0.98.5
Reporter: Jerry He

 Users have been asking for this. We have an internal requirement for this as 
 well.
 The goal is a provide a Admin API (and shell command) so that users can 
 request to split a region or table and get the split completion result 
 synchronously.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-2949) Add synchronous compact/split/flush or add a callback that gets pulled when compact/split/flush completes (and a progressable on how much is done)


[ 
https://issues.apache.org/jira/browse/HBASE-2949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078340#comment-14078340
 ] 

Jerry He commented on HBASE-2949:
-

Opened HBASE-11608

 Add synchronous compact/split/flush or add a callback that gets pulled when 
 compact/split/flush completes (and a progressable on how much is done)
 --

 Key: HBASE-2949
 URL: https://issues.apache.org/jira/browse/HBASE-2949
 Project: HBase
  Issue Type: New Feature
Reporter: stack

 Users have asked for this w/ a while.  They start a major compaction and are 
 a little baffled when the shell returns immediately.  We need to make the 
 call synchronous or add a callback or provide a progressable so user can see 
 how complete the task is.  Should we include a cancel task?  Hey! Why did 
 everything go slow of a sudden?  5 minutes later A major compaction 
 started on hbase... how do we turn it off?
 The need for this feature was also mentioned in HBASE-2701



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11474) [Thrift2] support authentication/impersonation


[ 
https://issues.apache.org/jira/browse/HBASE-11474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078355#comment-14078355
 ] 

Hudson commented on HBASE-11474:


FAILURE: Integrated in HBase-1.0 #74 (See 
[https://builds.apache.org/job/HBase-1.0/74/])
HBASE-11540 Document HBASE-11474 (Misty Stanley-Jones) (jxiang: rev 
90eb08eda58f5d921f4c311cfd50ae55dbb1b7d6)
* src/main/docbkx/security.xml
* src/main/docbkx/thrift_filter_language.xml


 [Thrift2] support authentication/impersonation
 --

 Key: HBASE-11474
 URL: https://issues.apache.org/jira/browse/HBASE-11474
 Project: HBase
  Issue Type: Improvement
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
 Fix For: 0.99.0, 0.98.4, 2.0.0

 Attachments: hbase-11474.patch, hbase-11474_1.patch


 This is to do the same as HBASE-11349 for Thrift2.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11540) Document HBASE-11474


[ 
https://issues.apache.org/jira/browse/HBASE-11540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078356#comment-14078356
 ] 

Hudson commented on HBASE-11540:


FAILURE: Integrated in HBase-1.0 #74 (See 
[https://builds.apache.org/job/HBase-1.0/74/])
HBASE-11540 Document HBASE-11474 (Misty Stanley-Jones) (jxiang: rev 
90eb08eda58f5d921f4c311cfd50ae55dbb1b7d6)
* src/main/docbkx/security.xml
* src/main/docbkx/thrift_filter_language.xml


 Document HBASE-11474
 

 Key: HBASE-11540
 URL: https://issues.apache.org/jira/browse/HBASE-11540
 Project: HBase
  Issue Type: Bug
  Components: documentation
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
Priority: Critical
 Fix For: 1.0.0, 2.0.0

 Attachments: HBASE-11540-1.patch, HBASE-11540.patch






--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HBASE-11606) Enable ZK-less region assignment by default


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

Jimmy Xiang updated HBASE-11606:


Attachment: hbase-11606.patch

 Enable ZK-less region assignment by default
 ---

 Key: HBASE-11606
 URL: https://issues.apache.org/jira/browse/HBASE-11606
 Project: HBase
  Issue Type: Task
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Priority: Minor
 Fix For: 2.0.0

 Attachments: hbase-11606.patch


 Let's enable ZK-less region assignment by default in the master branch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HBASE-11606) Enable ZK-less region assignment by default


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

Jimmy Xiang updated HBASE-11606:


Status: Patch Available  (was: Open)

 Enable ZK-less region assignment by default
 ---

 Key: HBASE-11606
 URL: https://issues.apache.org/jira/browse/HBASE-11606
 Project: HBase
  Issue Type: Task
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Priority: Minor
 Fix For: 2.0.0

 Attachments: hbase-11606.patch


 Let's enable ZK-less region assignment by default in the master branch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11606) Enable ZK-less region assignment by default

2014-07-29 Thread Mikhail Antonov (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078372#comment-14078372
 ] 

Mikhail Antonov commented on HBASE-11606:
-

Looks good to me. No changes in tests are needed, when this value is used? Like 
TestMasterFailover?

 Enable ZK-less region assignment by default
 ---

 Key: HBASE-11606
 URL: https://issues.apache.org/jira/browse/HBASE-11606
 Project: HBase
  Issue Type: Task
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Priority: Minor
 Fix For: 2.0.0

 Attachments: hbase-11606.patch


 Let's enable ZK-less region assignment by default in the master branch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11558) Caching set on Scan object gets lost when using TableMapReduceUtil in 0.95+

2014-07-29 Thread Ishan Chhabra (JIRA)

[
https://issues.apache.org/jira/browse/HBASE-11558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078381#comment-14078381
]

Ishan Chhabra commented on HBASE-11558:
---

Test failures are due to HBASE-11316

Caching set on Scan object gets lost when using TableMapReduceUtil in 0.95+
---

Attachments: HBASE_11558-0.96.patch, HBASE_11558-0.96_v2.patch,
HBASE_11558-0.98.patch, HBASE_11558-0.98_v2.patch, HBASE_11558.patch,
HBASE_11558_v2.patch, HBASE_11558_v2.patch

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11558) Caching set on Scan object gets lost when using TableMapReduceUtil in 0.95+

2014-07-29 Thread Ishan Chhabra (JIRA)

[
https://issues.apache.org/jira/browse/HBASE-11558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078385#comment-14078385
]

Ishan Chhabra commented on HBASE-11558:
---

[~apurtell], how can I trigger the build for 0.96 and 0.98 patches?

Caching set on Scan object gets lost when using TableMapReduceUtil in 0.95+
---

Attachments: HBASE_11558-0.96.patch, HBASE_11558-0.96_v2.patch,
HBASE_11558-0.98.patch, HBASE_11558-0.98_v2.patch, HBASE_11558.patch,
HBASE_11558_v2.patch, HBASE_11558_v2.patch

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11558) Caching set on Scan object gets lost when using TableMapReduceUtil in 0.95+

[
https://issues.apache.org/jira/browse/HBASE-11558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078391#comment-14078391
]

Andrew Purtell commented on HBASE-11558:

You cannot. Precommit builds always check out trunk. The test failures reported
in the last precommit build do not look related.

+1 for commit

Caching set on Scan object gets lost when using TableMapReduceUtil in 0.95+
---

Attachments: HBASE_11558-0.96.patch, HBASE_11558-0.96_v2.patch,
HBASE_11558-0.98.patch, HBASE_11558-0.98_v2.patch, HBASE_11558.patch,
HBASE_11558_v2.patch, HBASE_11558_v2.patch

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11609) LoadIncrementalHFiles fails if the namespace is specified

2014-07-29 Thread Ted Yu (JIRA)


[ 
https://issues.apache.org/jira/browse/HBASE-11609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078419#comment-14078419
 ] 

Ted Yu commented on HBASE-11609:


{code}
+  private String getUniqueName(TableName tableName) {
{code}
unique name is not related to table name any more. tableName parameter can be 
omitted, right ?

 LoadIncrementalHFiles fails if the namespace is specified
 -

 Key: HBASE-11609
 URL: https://issues.apache.org/jira/browse/HBASE-11609
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 1.0.0, 0.98.4, 2.0.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
 Fix For: 1.0.0, 0.98.5, 2.0.0

 Attachments: HBASE-11609-v0.patch


 from Jianshi Huang on the user list
 trying to bulk load a table in a namespace, like:
 $ hbase org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles test/ 
 foo:testtb
 we get an exception
 {code}
 2014-07-29 19:59:53,373 ERROR [main] mapreduce.LoadIncrementalHFiles: 
 Unexpected execution exception during splitting
 java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: 
 java.net.URISyntaxException: Relative path in absolute URI: 
 foo:testtb,1.bottom
 at java.util.concurrent.FutureTask.report(FutureTask.java:122)
 at java.util.concurrent.FutureTask.get(FutureTask.java:188)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.groupOrSplitPhase(LoadIncrementalHFiles.java:449)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.doBulkLoad(LoadIncrementalHFiles.java:304)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.run(LoadIncrementalHFiles.java:899)
 at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
 at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
 {code}
 The problem is related to the ':' symbol going to the file path. the simple 
 fix is to replace the current LoadIncrementalHFiles.getUniqueName()



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11606) Enable ZK-less region assignment by default

[
https://issues.apache.org/jira/browse/HBASE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078428#comment-14078428
]

Hadoop QA commented on HBASE-11606:
---

{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12658486/hbase-11606.patch
against trunk revision .
ATTACHMENT ID: 12658486

{color:green}+1 @author{color}. The patch does not contain any @author
tags.

{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.

{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.

{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.

{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.

{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100

{color:green}+1 site{color}. The mvn site goal succeeds with this patch.

{color:red}-1 core tests{color}. The patch failed these unit tests:

org.apache.hadoop.hbase.regionserver.compactions.TestStripeCompactionPolicy

org.apache.hadoop.hbase.regionserver.TestDefaultCompactSelection

Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/10217//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10217//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10217//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10217//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10217//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10217//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10217//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10217//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10217//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/10217//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/10217//console

This message is automatically generated.

Enable ZK-less region assignment by default
---

Key: HBASE-11606
URL: https://issues.apache.org/jira/browse/HBASE-11606
Project: HBase
Issue Type: Task
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Priority: Minor
Fix For: 2.0.0

Attachments: hbase-11606.patch

Let's enable ZK-less region assignment by default in the master branch.

--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (HBASE-11609) LoadIncrementalHFiles fails if the namespace is specified


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

Matteo Bertozzi updated HBASE-11609:


Attachment: HBASE-11609-v1.patch

 LoadIncrementalHFiles fails if the namespace is specified
 -

 Key: HBASE-11609
 URL: https://issues.apache.org/jira/browse/HBASE-11609
 Project: HBase
  Issue Type: Bug
  Components: Client
Affects Versions: 1.0.0, 0.98.4, 2.0.0
Reporter: Matteo Bertozzi
Assignee: Matteo Bertozzi
 Fix For: 1.0.0, 0.98.5, 2.0.0

 Attachments: HBASE-11609-v0.patch, HBASE-11609-v1.patch


 from Jianshi Huang on the user list
 trying to bulk load a table in a namespace, like:
 $ hbase org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles test/ 
 foo:testtb
 we get an exception
 {code}
 2014-07-29 19:59:53,373 ERROR [main] mapreduce.LoadIncrementalHFiles: 
 Unexpected execution exception during splitting
 java.util.concurrent.ExecutionException: java.lang.IllegalArgumentException: 
 java.net.URISyntaxException: Relative path in absolute URI: 
 foo:testtb,1.bottom
 at java.util.concurrent.FutureTask.report(FutureTask.java:122)
 at java.util.concurrent.FutureTask.get(FutureTask.java:188)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.groupOrSplitPhase(LoadIncrementalHFiles.java:449)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.doBulkLoad(LoadIncrementalHFiles.java:304)
 at 
 org.apache.hadoop.hbase.mapreduce.LoadIncrementalHFiles.run(LoadIncrementalHFiles.java:899)
 at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
 at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:84)
 {code}
 The problem is related to the ':' symbol going to the file path. the simple 
 fix is to replace the current LoadIncrementalHFiles.getUniqueName()



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11606) Enable ZK-less region assignment by default


[ 
https://issues.apache.org/jira/browse/HBASE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078505#comment-14078505
 ] 

stack commented on HBASE-11606:
---

+1

Failures are not yours.

 Enable ZK-less region assignment by default
 ---

 Key: HBASE-11606
 URL: https://issues.apache.org/jira/browse/HBASE-11606
 Project: HBase
  Issue Type: Task
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Priority: Minor
 Fix For: 2.0.0

 Attachments: hbase-11606.patch


 Let's enable ZK-less region assignment by default in the master branch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11606) Enable ZK-less region assignment by default


[ 
https://issues.apache.org/jira/browse/HBASE-11606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14078506#comment-14078506
 ] 

stack commented on HBASE-11606:
---

Needs a release note.

 Enable ZK-less region assignment by default
 ---

 Key: HBASE-11606
 URL: https://issues.apache.org/jira/browse/HBASE-11606
 Project: HBase
  Issue Type: Task
Reporter: Jimmy Xiang
Assignee: Jimmy Xiang
Priority: Minor
 Fix For: 2.0.0

 Attachments: hbase-11606.patch


 Let's enable ZK-less region assignment by default in the master branch.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (HBASE-11610) Enhance remote meta updates

Jimmy Xiang created HBASE-11610:
---

 Summary: Enhance remote meta updates
 Key: HBASE-11610
 URL: https://issues.apache.org/jira/browse/HBASE-11610
 Project: HBase
  Issue Type: Improvement
Reporter: Jimmy Xiang


Currently, if the meta region is on a regionserver instead of the master, meta 
update is synchronized on one HTable instance. We should be able to do better.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (HBASE-11609) LoadIncrementalHFiles fails if the namespace is specified