[jira] [Commented] (HBASE-11276) Add back support for running ChaosMonkey as standalone tool
[ https://issues.apache.org/jira/browse/HBASE-11276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640010#comment-14640010 ] Hudson commented on HBASE-11276: FAILURE: Integrated in HBase-1.3 #73 (See [https://builds.apache.org/job/HBase-1.3/73/]) HBASE-11276 Add back support for running ChaosMonkey as standalone tool (Yu Li) (enis: rev 4a041fd837f30e90384d06a825b4db82c6be0838) * hbase-it/src/test/java/org/apache/hadoop/hbase/chaos/util/ChaosMonkeyRunner.java * hbase-it/src/test/java/org/apache/hadoop/hbase/IntegrationTestingUtility.java Add back support for running ChaosMonkey as standalone tool --- Key: HBASE-11276 URL: https://issues.apache.org/jira/browse/HBASE-11276 Project: HBase Issue Type: Task Affects Versions: 0.98.0, 0.96.0, 0.99.0 Reporter: Dima Spivak Assignee: Yu Li Priority: Minor Fix For: 2.0.0, 1.0.2, 1.2.0, 1.1.2, 1.3.0 Attachments: HBASE-11276-0.98.patch, HBASE-11276.patch, HBASE-11276_v2.patch, HBASE-11276_v3.patch, HBASE-11276_v4.patch [According to the ref guide|http://hbase.apache.org/book/hbase.tests.html#integration.tests], it was once possible to run ChaosMonkey as a standalone tool against a deployed cluster. After 0.94, this is no longer possible. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14122) Client API for determining if server side supports cell level security
[
https://issues.apache.org/jira/browse/HBASE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640058#comment-14640058
]
Hadoop QA commented on HBASE-14122:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746941/HBASE-14122-v2-0.98.patch
against 0.98 branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12746941
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 8 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated
25 warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
3878 checkstyle errors (more than the master's current 3877 errors).
{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:
+ * coderpc getSecurityCapabilities(.SecurityCapabilitiesRequest)
returns (.SecurityCapabilitiesResponse);/code
+ * coderpc getSecurityCapabilities(.SecurityCapabilitiesRequest) returns
(.SecurityCapabilitiesResponse);/code
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.security.access.TestWithDisabledAuthorization
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14879//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14879//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14879//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14879//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14879//console
This message is automatically generated.
Client API for determining if server side supports cell level security
--
Key: HBASE-14122
URL: https://issues.apache.org/jira/browse/HBASE-14122
Project: HBase
Issue Type: Improvement
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 2.0.0, 0.98.14, 1.2.0, 1.3.0
Attachments: HBASE-14122-v2-0.98.patch,
HBASE-14122-v2-branch-1.patch, HBASE-14122-v2.patch, HBASE-14122.patch
Add a client API for determining if the server side supports cell level
security.
Ask the master, assuming as we do in many other instances that the master and
regionservers all have a consistent view of site configuration.
Return {{true}} if all features required for cell level security are present,
{{false}} otherwise, or throw {{UnsupportedOperationException}} if the master
does not have support for the RPC call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14063) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
[
https://issues.apache.org/jira/browse/HBASE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640079#comment-14640079
]
Hadoop QA commented on HBASE-14063:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746944/HBASE-14063_1.patch
against master branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12746944
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 7 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{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 post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.master.TestDistributedLogSplitting
{color:red}-1 core zombie tests{color}. There are 5 zombie test(s):
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testExportFileSystemState(TestExportSnapshot.java:288)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testExportFileSystemState(TestExportSnapshot.java:262)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testSnapshotWithRefsExportFileSystemState(TestExportSnapshot.java:256)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testSnapshotWithRefsExportFileSystemState(TestExportSnapshot.java:240)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportFileSystemState(TestMobExportSnapshot.java:285)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportFileSystemState(TestMobExportSnapshot.java:259)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportFileSystemState(TestMobExportSnapshot.java:192)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testExportFileSystemState(TestExportSnapshot.java:288)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testExportFileSystemState(TestExportSnapshot.java:262)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testSnapshotWithRefsExportFileSystemState(TestExportSnapshot.java:256)
at
org.apache.hadoop.hbase.snapshot.TestExportSnapshot.testSnapshotWithRefsExportFileSystemState(TestExportSnapshot.java:236)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportFileSystemState(TestMobExportSnapshot.java:285)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportFileSystemState(TestMobExportSnapshot.java:259)
at
org.apache.hadoop.hbase.snapshot.TestMobExportSnapshot.testExportFileSystemState(TestMobExportSnapshot.java:192)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14880//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14880//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14880//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14880//console
This message is automatically generated.
Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
---
Key: HBASE-14063
URL: https://issues.apache.org/jira/browse/HBASE-14063
Project: HBase
Issue Type: Sub-task
Components: regionserver, Scanners
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Fix For: 2.0.0
Attachments: HBASE-14063.patch, HBASE-14063_1.patch
Subtask to ensure that the BytebufferBackedCell gets used in the read path
after HBASE-12213 and HBASE-12295 goes in. This would help to clearly change
the required places and makes the review easier.
--
This message was sent by Atlassian JIRA
[jira] [Assigned] (HBASE-14057) HBase shell user_permission should list super users defined on hbase-site.xml
[
https://issues.apache.org/jira/browse/HBASE-14057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Srungarapu reassigned HBASE-14057:
---
Assignee: Srikanth Srungarapu
HBase shell user_permission should list super users defined on hbase-site.xml
-
Key: HBASE-14057
URL: https://issues.apache.org/jira/browse/HBASE-14057
Project: HBase
Issue Type: Task
Components: shell
Affects Versions: 1.0.1
Reporter: Wellington Chevreuil
Assignee: Srikanth Srungarapu
Priority: Minor
Attachments: HBASE-14057.patch
On HBase Shell, user_permission command without specifying any user lists all
users granted global permissions (grant 'user', 'RWXCA'):
{noformat}
hbase(main):008:0* user_permission
User
Namespace,Table,Family,Qualifier:Permission
@hbase-admin hbase,hbase:acl,,:
[Permission: actions=READ,WRITE,EXEC,CREATE,ADMIN]
1 row(s) in 3.1710 seconds
{noformat}
Users defined as super users on hbase-site.xml configuration file are not
listed by this same command, even though a super user has the same
permissions/privileges as those defined through grant 'user', 'RWXCA'
command on the shell:
{noformat}
property
namehbase.superuser/name
valuehbase-user/value
/property
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14057) HBase shell user_permission should list super users defined on hbase-site.xml
[
https://issues.apache.org/jira/browse/HBASE-14057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Srungarapu updated HBASE-14057:
Attachment: (was: HBASE-14057.patch)
HBase shell user_permission should list super users defined on hbase-site.xml
-
Key: HBASE-14057
URL: https://issues.apache.org/jira/browse/HBASE-14057
Project: HBase
Issue Type: Task
Components: shell
Affects Versions: 1.0.1
Reporter: Wellington Chevreuil
Assignee: Srikanth Srungarapu
Priority: Minor
Attachments: HBASE-14057-branch-1.patch
On HBase Shell, user_permission command without specifying any user lists all
users granted global permissions (grant 'user', 'RWXCA'):
{noformat}
hbase(main):008:0* user_permission
User
Namespace,Table,Family,Qualifier:Permission
@hbase-admin hbase,hbase:acl,,:
[Permission: actions=READ,WRITE,EXEC,CREATE,ADMIN]
1 row(s) in 3.1710 seconds
{noformat}
Users defined as super users on hbase-site.xml configuration file are not
listed by this same command, even though a super user has the same
permissions/privileges as those defined through grant 'user', 'RWXCA'
command on the shell:
{noformat}
property
namehbase.superuser/name
valuehbase-user/value
/property
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14057) HBase shell user_permission should list super users defined on hbase-site.xml
[
https://issues.apache.org/jira/browse/HBASE-14057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Srungarapu updated HBASE-14057:
Attachment: HBASE-14057-branch-1.patch
HBase shell user_permission should list super users defined on hbase-site.xml
-
Key: HBASE-14057
URL: https://issues.apache.org/jira/browse/HBASE-14057
Project: HBase
Issue Type: Task
Components: shell
Affects Versions: 1.0.1
Reporter: Wellington Chevreuil
Assignee: Srikanth Srungarapu
Priority: Minor
Attachments: HBASE-14057-branch-1.patch
On HBase Shell, user_permission command without specifying any user lists all
users granted global permissions (grant 'user', 'RWXCA'):
{noformat}
hbase(main):008:0* user_permission
User
Namespace,Table,Family,Qualifier:Permission
@hbase-admin hbase,hbase:acl,,:
[Permission: actions=READ,WRITE,EXEC,CREATE,ADMIN]
1 row(s) in 3.1710 seconds
{noformat}
Users defined as super users on hbase-site.xml configuration file are not
listed by this same command, even though a super user has the same
permissions/privileges as those defined through grant 'user', 'RWXCA'
command on the shell:
{noformat}
property
namehbase.superuser/name
valuehbase-user/value
/property
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Work started] (HBASE-14057) HBase shell user_permission should list super users defined on hbase-site.xml
[
https://issues.apache.org/jira/browse/HBASE-14057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HBASE-14057 started by Srikanth Srungarapu.
---
HBase shell user_permission should list super users defined on hbase-site.xml
-
Key: HBASE-14057
URL: https://issues.apache.org/jira/browse/HBASE-14057
Project: HBase
Issue Type: Task
Components: shell
Affects Versions: 1.0.1
Reporter: Wellington Chevreuil
Assignee: Srikanth Srungarapu
Priority: Minor
Attachments: HBASE-14057-branch-1.patch
On HBase Shell, user_permission command without specifying any user lists all
users granted global permissions (grant 'user', 'RWXCA'):
{noformat}
hbase(main):008:0* user_permission
User
Namespace,Table,Family,Qualifier:Permission
@hbase-admin hbase,hbase:acl,,:
[Permission: actions=READ,WRITE,EXEC,CREATE,ADMIN]
1 row(s) in 3.1710 seconds
{noformat}
Users defined as super users on hbase-site.xml configuration file are not
listed by this same command, even though a super user has the same
permissions/privileges as those defined through grant 'user', 'RWXCA'
command on the shell:
{noformat}
property
namehbase.superuser/name
valuehbase-user/value
/property
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14063) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
[ https://issues.apache.org/jira/browse/HBASE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639998#comment-14639998 ] ramkrishna.s.vasudevan commented on HBASE-14063: RB link - https://reviews.apache.org/r/36765/ Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295 --- Key: HBASE-14063 URL: https://issues.apache.org/jira/browse/HBASE-14063 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-14063.patch, HBASE-14063_1.patch Subtask to ensure that the BytebufferBackedCell gets used in the read path after HBASE-12213 and HBASE-12295 goes in. This would help to clearly change the required places and makes the review easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14122) Client API for determining if server side supports cell level security
[
https://issues.apache.org/jira/browse/HBASE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640017#comment-14640017
]
Hadoop QA commented on HBASE-14122:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746940/HBASE-14122-v2-branch-1.patch
against branch-1 branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12746940
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 8 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
3826 checkstyle errors (more than the master's current 3825 errors).
{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:
+ * coderpc
getSecurityCapabilities(.hbase.pb.SecurityCapabilitiesRequest) returns
(.hbase.pb.SecurityCapabilitiesResponse);/code
+ * coderpc
getSecurityCapabilities(.hbase.pb.SecurityCapabilitiesRequest) returns
(.hbase.pb.SecurityCapabilitiesResponse);/code
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.security.access.TestWithDisabledAuthorization
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.camel.processor.RedeliveryOnExceptionBlockedDelayTest.testRedelivery(RedeliveryOnExceptionBlockedDelayTest.java:47)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14878//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14878//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14878//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14878//console
This message is automatically generated.
Client API for determining if server side supports cell level security
--
Key: HBASE-14122
URL: https://issues.apache.org/jira/browse/HBASE-14122
Project: HBase
Issue Type: Improvement
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 2.0.0, 0.98.14, 1.2.0, 1.3.0
Attachments: HBASE-14122-v2-0.98.patch,
HBASE-14122-v2-branch-1.patch, HBASE-14122-v2.patch, HBASE-14122.patch
Add a client API for determining if the server side supports cell level
security.
Ask the master, assuming as we do in many other instances that the master and
regionservers all have a consistent view of site configuration.
Return {{true}} if all features required for cell level security are present,
{{false}} otherwise, or throw {{UnsupportedOperationException}} if the master
does not have support for the RPC call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13992) Integrate SparkOnHBase into HBase
[
https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14639984#comment-14639984
]
Hadoop QA commented on HBASE-13992:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746933/HBASE-13992.10.patch
against master branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12746933
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:red}-1 javac{color}. The applied patch generated 26 javac compiler
warnings (more than the master's current 24 warnings).
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 2
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{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 post-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 3 zombie test(s):
at
org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDeletes.testDeleteFamilyLatestTimeStampWithMulipleVersionsWithoutCellVisibilityInPuts(TestVisibilityLabelsWithDeletes.java:1511)
at
org.apache.hadoop.hbase.coprocessor.TestOpenTableInCoprocessor.testCoprocessorCanCreateConnectionToRemoteTableWithCustomPool(TestOpenTableInCoprocessor.java:145)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14876//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14876//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14876//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14876//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14876//console
This message is automatically generated.
Integrate SparkOnHBase into HBase
-
Key: HBASE-13992
URL: https://issues.apache.org/jira/browse/HBASE-13992
Project: HBase
Issue Type: New Feature
Components: spark
Reporter: Ted Malaska
Assignee: Ted Malaska
Fix For: 2.0.0
Attachments: HBASE-13992.10.patch, HBASE-13992.5.patch,
HBASE-13992.6.patch, HBASE-13992.7.patch, HBASE-13992.8.patch,
HBASE-13992.9.patch, HBASE-13992.patch, HBASE-13992.patch.3,
HBASE-13992.patch.4, HBASE-13992.patch.5
This Jira is to ask if SparkOnHBase can find a home in side HBase core.
Here is the github:
https://github.com/cloudera-labs/SparkOnHBase
I am the core author of this project and the license is Apache 2.0
A blog explaining this project is here
http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/
A spark Streaming example is here
http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/
A real customer using this in produce is blogged here
http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/
Please debate and let me know what I can do to make this happen.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14057) HBase shell user_permission should list super users defined on hbase-site.xml
[
https://issues.apache.org/jira/browse/HBASE-14057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Srungarapu updated HBASE-14057:
Attachment: HBASE-14057.patch
HBase shell user_permission should list super users defined on hbase-site.xml
-
Key: HBASE-14057
URL: https://issues.apache.org/jira/browse/HBASE-14057
Project: HBase
Issue Type: Task
Components: shell
Affects Versions: 1.0.1
Reporter: Wellington Chevreuil
Priority: Minor
Attachments: HBASE-14057.patch
On HBase Shell, user_permission command without specifying any user lists all
users granted global permissions (grant 'user', 'RWXCA'):
{noformat}
hbase(main):008:0* user_permission
User
Namespace,Table,Family,Qualifier:Permission
@hbase-admin hbase,hbase:acl,,:
[Permission: actions=READ,WRITE,EXEC,CREATE,ADMIN]
1 row(s) in 3.1710 seconds
{noformat}
Users defined as super users on hbase-site.xml configuration file are not
listed by this same command, even though a super user has the same
permissions/privileges as those defined through grant 'user', 'RWXCA'
command on the shell:
{noformat}
property
namehbase.superuser/name
valuehbase-user/value
/property
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14122) Client API for determining if server side supports cell level security
[
https://issues.apache.org/jira/browse/HBASE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640025#comment-14640025
]
Hadoop QA commented on HBASE-14122:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746938/HBASE-14122-v2.patch
against master branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12746938
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 8 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
1867 checkstyle errors (more than the master's current 1866 errors).
{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:
+ * coderpc
getSecurityCapabilities(.hbase.pb.SecurityCapabilitiesRequest) returns
(.hbase.pb.SecurityCapabilitiesResponse);/code
+ * coderpc
getSecurityCapabilities(.hbase.pb.SecurityCapabilitiesRequest) returns
(.hbase.pb.SecurityCapabilitiesResponse);/code
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.security.access.TestWithDisabledAuthorization
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.coprocessor.TestOpenTableInCoprocessor.testCoprocessorCanCreateConnectionToRemoteTableWithCustomPool(TestOpenTableInCoprocessor.java:145)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14877//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14877//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14877//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14877//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14877//console
This message is automatically generated.
Client API for determining if server side supports cell level security
--
Key: HBASE-14122
URL: https://issues.apache.org/jira/browse/HBASE-14122
Project: HBase
Issue Type: Improvement
Reporter: Andrew Purtell
Assignee: Andrew Purtell
Priority: Minor
Fix For: 2.0.0, 0.98.14, 1.2.0, 1.3.0
Attachments: HBASE-14122-v2-0.98.patch,
HBASE-14122-v2-branch-1.patch, HBASE-14122-v2.patch, HBASE-14122.patch
Add a client API for determining if the server side supports cell level
security.
Ask the master, assuming as we do in many other instances that the master and
regionservers all have a consistent view of site configuration.
Return {{true}} if all features required for cell level security are present,
{{false}} otherwise, or throw {{UnsupportedOperationException}} if the master
does not have support for the RPC call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14057) HBase shell user_permission should list super users defined on hbase-site.xml
[
https://issues.apache.org/jira/browse/HBASE-14057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640030#comment-14640030
]
Srikanth Srungarapu commented on HBASE-14057:
-
Discussed this with [~mbertozzi] offline. The output will be like
{code}
hbase(main):008:0* user_permission
User Namespace,Table,Family,Qualifier:Permission
superuser1hbase,hbase:acl,,: [Permission:
actions=READ,WRITE,EXEC,CREATE]
superuser2hbase,hbase:acl,,: [Permission:
actions=READ,WRITE,EXEC,CREATE]
...
{code}
HBase shell user_permission should list super users defined on hbase-site.xml
-
Key: HBASE-14057
URL: https://issues.apache.org/jira/browse/HBASE-14057
Project: HBase
Issue Type: Task
Components: shell
Affects Versions: 1.0.1
Reporter: Wellington Chevreuil
Assignee: Srikanth Srungarapu
Priority: Minor
Attachments: HBASE-14057-branch-1.patch
On HBase Shell, user_permission command without specifying any user lists all
users granted global permissions (grant 'user', 'RWXCA'):
{noformat}
hbase(main):008:0* user_permission
User
Namespace,Table,Family,Qualifier:Permission
@hbase-admin hbase,hbase:acl,,:
[Permission: actions=READ,WRITE,EXEC,CREATE,ADMIN]
1 row(s) in 3.1710 seconds
{noformat}
Users defined as super users on hbase-site.xml configuration file are not
listed by this same command, even though a super user has the same
permissions/privileges as those defined through grant 'user', 'RWXCA'
command on the shell:
{noformat}
property
namehbase.superuser/name
valuehbase-user/value
/property
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingcheng Du updated HBASE-14152: - Attachment: HBASE-14152-V3.patch Upload a new patch V3, no new tests are included. # Suppress the warning in FindBugs. Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152-V3.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640073#comment-14640073 ] ramkrishna.s.vasudevan commented on HBASE-14152: +1 Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152-V3.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14070) Hybrid Logical Clocks for HBase
[ https://issues.apache.org/jira/browse/HBASE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640219#comment-14640219 ] stack commented on HBASE-14070: --- Nice javadoc Timestamps from cells should always be interpreted by the table's Timestamp type so that timestamps given by HBase servers can be converted to wall clock. This implies Cell is no longer standalone. It needs a context so its timestamp is interpreted appropriately. Hybrid Logical Clocks for HBase --- Key: HBASE-14070 URL: https://issues.apache.org/jira/browse/HBASE-14070 Project: HBase Issue Type: New Feature Reporter: Enis Soztutar Assignee: Enis Soztutar Attachments: HybridLogicalClocksforHBaseandPhoenix.docx, HybridLogicalClocksforHBaseandPhoenix.pdf HBase and Phoenix uses systems physical clock (PT) to give timestamps to events (read and writes). This works mostly when the system clock is strictly monotonically increasing and there is no cross-dependency between servers clocks. However we know that leap seconds, general clock skew and clock drift are in fact real. This jira proposes using Hybrid Logical Clocks (HLC) as an implementation of hybrid physical clock + a logical clock. HLC is best of both worlds where it keeps causality relationship similar to logical clocks, but still is compatible with NTP based physical system clock. HLC can be represented in 64bits. A design document is attached and also can be found here: https://docs.google.com/document/d/1LL2GAodiYi0waBz5ODGL4LDT4e_bXy8P9h6kWC05Bhw/edit# -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14070) Hybrid Logical Clocks for HBase
[ https://issues.apache.org/jira/browse/HBASE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640214#comment-14640214 ] stack commented on HBASE-14070: --- I put a comment in the doc asking how time and sequenceid relate. If time were by region rather than by regionserver, HLC time could be the sequenceid as I see it. Dave Latham followed up with a suggestion on how we might deal with clients that set the timestamp explicitly that may be more generally applicable. Hybrid Logical Clocks for HBase --- Key: HBASE-14070 URL: https://issues.apache.org/jira/browse/HBASE-14070 Project: HBase Issue Type: New Feature Reporter: Enis Soztutar Assignee: Enis Soztutar Attachments: HybridLogicalClocksforHBaseandPhoenix.docx, HybridLogicalClocksforHBaseandPhoenix.pdf HBase and Phoenix uses systems physical clock (PT) to give timestamps to events (read and writes). This works mostly when the system clock is strictly monotonically increasing and there is no cross-dependency between servers clocks. However we know that leap seconds, general clock skew and clock drift are in fact real. This jira proposes using Hybrid Logical Clocks (HLC) as an implementation of hybrid physical clock + a logical clock. HLC is best of both worlds where it keeps causality relationship similar to logical clocks, but still is compatible with NTP based physical system clock. HLC can be represented in 64bits. A design document is attached and also can be found here: https://docs.google.com/document/d/1LL2GAodiYi0waBz5ODGL4LDT4e_bXy8P9h6kWC05Bhw/edit# -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14063) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
[ https://issues.apache.org/jira/browse/HBASE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-14063: --- Status: Open (was: Patch Available) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295 --- Key: HBASE-14063 URL: https://issues.apache.org/jira/browse/HBASE-14063 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-14063.patch, HBASE-14063_1.patch Subtask to ensure that the BytebufferBackedCell gets used in the read path after HBASE-12213 and HBASE-12295 goes in. This would help to clearly change the required places and makes the review easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingcheng Du updated HBASE-14152: - Attachment: HBASE-14152-V3.patch Re-attach the patch V3 to trigger the hadoop QA. Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152-V3.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingcheng Du updated HBASE-14152: - Attachment: (was: HBASE-14152-V3.patch) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152-V3.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14063) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
[ https://issues.apache.org/jira/browse/HBASE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-14063: --- Attachment: HBASE-14063_3.patch Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295 --- Key: HBASE-14063 URL: https://issues.apache.org/jira/browse/HBASE-14063 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-14063.patch, HBASE-14063_1.patch, HBASE-14063_3.patch Subtask to ensure that the BytebufferBackedCell gets used in the read path after HBASE-12213 and HBASE-12295 goes in. This would help to clearly change the required places and makes the review easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14063) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
[ https://issues.apache.org/jira/browse/HBASE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-14063: --- Status: Patch Available (was: Open) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295 --- Key: HBASE-14063 URL: https://issues.apache.org/jira/browse/HBASE-14063 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-14063.patch, HBASE-14063_1.patch, HBASE-14063_3.patch Subtask to ensure that the BytebufferBackedCell gets used in the read path after HBASE-12213 and HBASE-12295 goes in. This would help to clearly change the required places and makes the review easier. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14154) DFS Replication should be configurable at column family level
[
https://issues.apache.org/jira/browse/HBASE-14154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640338#comment-14640338
]
Ashish Singhi commented on HBASE-14154:
---
Added a new configuration property {{DFS_REPLICATION}} for column family
descriptor.
Tested on one node cluster (RF set 1)
1. With default deplication
2. Create a table with one family with DFS_REPLICATION is set to 3, saw two
missing replicas for it in HDFS fsck report
3. Create a table with one family with DFS_REPLICATION is set to 3 and the
other with default replication, again saw two new missing replicas for it in
HDFS fsck report for the family with RF set to 3.
4. Create table with DFS_REPLICATION = 0, it fails
Please review.
DFS Replication should be configurable at column family level
-
Key: HBASE-14154
URL: https://issues.apache.org/jira/browse/HBASE-14154
Project: HBase
Issue Type: New Feature
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Priority: Minor
Attachments: HBASE-14154.patch
There are cases where a user wants to have a control on the number of hfile
copies he/she can have in the cluster.
For eg: For a test table user would like to have only one copy instead of
three(default).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[
https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640324#comment-14640324
]
Hadoop QA commented on HBASE-14152:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746972/HBASE-14152-V3.patch
against master branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12746972
{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 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{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 post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14881//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14881//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14881//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14881//console
This message is automatically generated.
Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
-
Key: HBASE-14152
URL: https://issues.apache.org/jira/browse/HBASE-14152
Project: HBase
Issue Type: Improvement
Components: mob
Affects Versions: 2.0.0
Reporter: Jingcheng Du
Assignee: Jingcheng Du
Fix For: 2.0.0
Attachments: HBASE-14152-V2.patch, HBASE-14152-V3.patch,
HBASE-14152.patch
There are some new warnings in Checkstyle and FindBugs brought in by merging
the feature branch hbase-11339 to trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-14154) DFS Replication should be configurable at column family level
Ashish Singhi created HBASE-14154: - Summary: DFS Replication should be configurable at column family level Key: HBASE-14154 URL: https://issues.apache.org/jira/browse/HBASE-14154 Project: HBase Issue Type: New Feature Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor There are cases where a user wants to have a control on the number of hfile copies he/she can have in the cluster. For eg: For a test table user would like to have only one copy instead of three(default). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14154) DFS Replication should be configurable at column family level
[ https://issues.apache.org/jira/browse/HBASE-14154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singhi updated HBASE-14154: -- Attachment: HBASE-14154.patch DFS Replication should be configurable at column family level - Key: HBASE-14154 URL: https://issues.apache.org/jira/browse/HBASE-14154 Project: HBase Issue Type: New Feature Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor Attachments: HBASE-14154.patch There are cases where a user wants to have a control on the number of hfile copies he/she can have in the cluster. For eg: For a test table user would like to have only one copy instead of three(default). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14154) DFS Replication should be configurable at column family level
[ https://issues.apache.org/jira/browse/HBASE-14154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singhi updated HBASE-14154: -- Status: Patch Available (was: Open) DFS Replication should be configurable at column family level - Key: HBASE-14154 URL: https://issues.apache.org/jira/browse/HBASE-14154 Project: HBase Issue Type: New Feature Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor Attachments: HBASE-14154.patch There are cases where a user wants to have a control on the number of hfile copies he/she can have in the cluster. For eg: For a test table user would like to have only one copy instead of three(default). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HBASE-13657) Improve test run time
[
https://issues.apache.org/jira/browse/HBASE-13657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Singhi reassigned HBASE-13657:
-
Assignee: Ashish Singhi
Improve test run time
-
Key: HBASE-13657
URL: https://issues.apache.org/jira/browse/HBASE-13657
Project: HBase
Issue Type: Umbrella
Components: test
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Labels: beginner
In some tests we are doing some operations in {{@Before}} and {{@After}}
annotated methods which are not really required to be done before and after
every test run, instead we can move them in {{@BeforeClass}} and
{{@AfterClass}} annotated methods respectively and hence improve the test run
time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14105) Add shell tests for Snapshot
[
https://issues.apache.org/jira/browse/HBASE-14105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641049#comment-14641049
]
Hadoop QA commented on HBASE-14105:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12747064/HBASE-14105-0.98.patch
against 0.98 branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12747064
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 8 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated
24 warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{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 post-site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14885//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14885//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14885//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14885//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14885//console
This message is automatically generated.
Add shell tests for Snapshot
Key: HBASE-14105
URL: https://issues.apache.org/jira/browse/HBASE-14105
Project: HBase
Issue Type: Sub-task
Components: test
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0
Attachments: HBASE-14105-0.98.patch, HBASE-14105-branch-1.0.patch,
HBASE-14105.patch
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14069) Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm
[ https://issues.apache.org/jira/browse/HBASE-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641090#comment-14641090 ] Abhilash commented on HBASE-14069: -- Made changes according to Elliot's reviews. I wont be able to work on this for some time from now. If it has further code reviews I will pick it up some time later. Thanks a lot :) Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm -- Key: HBASE-14069 URL: https://issues.apache.org/jira/browse/HBASE-14069 Project: HBase Issue Type: New Feature Components: hbase, util Reporter: Elliott Clark Assignee: Abhilash Attachments: 0001-Improve-RegionSplitter-v1.patch, 0001-Improve-RegionSplitter.patch RegionSplittler is the utility that can rolling split regions. It would be nice to be able to split regions and have the normal split points get computed for me so that I'm not reliant on knowing data distribution. Tested manually on standalone mode for various test cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14154) DFS Replication should be configurable at column family level
[
https://issues.apache.org/jira/browse/HBASE-14154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640589#comment-14640589
]
Hadoop QA commented on HBASE-14154:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12747011/HBASE-14154.patch
against master branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12747011
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 20 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{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 post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.util.TestProcessBasedCluster
org.apache.hadoop.hbase.mapreduce.TestImportExport
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.coprocessor.TestOpenTableInCoprocessor.testCoprocessorCanCreateConnectionToRemoteTableWithCustomPool(TestOpenTableInCoprocessor.java:145)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14884//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14884//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14884//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14884//console
This message is automatically generated.
DFS Replication should be configurable at column family level
-
Key: HBASE-14154
URL: https://issues.apache.org/jira/browse/HBASE-14154
Project: HBase
Issue Type: New Feature
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Priority: Minor
Attachments: HBASE-14154.patch
There are cases where a user wants to have a control on the number of hfile
copies he/she can have in the cluster.
For eg: For a test table user would like to have only one copy instead of
three(default).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14024) ImportTsv is not loading hbase-default.xml
[
https://issues.apache.org/jira/browse/HBASE-14024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641039#comment-14641039
]
Hadoop QA commented on HBASE-14024:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12747069/HBASE-14024%282%29%20.patch
against master branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12747069
{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 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{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 post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestReplicasClient
{color:red}-1 core zombie tests{color}. There are 3 zombie test(s):
at
org.apache.camel.test.spring.CamelSpringTestSupport.doCreateApplicationContext(CamelSpringTestSupport.java:90)
at
org.apache.camel.test.spring.CamelSpringTestSupport.doPreSetup(CamelSpringTestSupport.java:80)
at
org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:216)
at
org.apache.camel.component.jetty.jettyproducer.HttpJettyProducerRecipientListCustomThreadPoolTest.testRecipientList(HttpJettyProducerRecipientListCustomThreadPoolTest.java:40)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14886//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14886//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14886//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14886//console
This message is automatically generated.
ImportTsv is not loading hbase-default.xml
--
Key: HBASE-14024
URL: https://issues.apache.org/jira/browse/HBASE-14024
Project: HBase
Issue Type: Bug
Components: mapreduce
Affects Versions: 2.0.0
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Priority: Critical
Fix For: 2.0.0
Attachments: HBASE-14024(1).patch, HBASE-14024(2) .patch,
HBASE-14024.patch
ImportTsv job is failing with below exception
{noformat}
Exception in thread main java.lang.IllegalArgumentException: Can not create
a Path from a null string
at org.apache.hadoop.fs.Path.checkPathArg(Path.java:123)
at org.apache.hadoop.fs.Path.init(Path.java:135)
at org.apache.hadoop.fs.Path.init(Path.java:89)
at
org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configurePartitioner(HFileOutputFormat2.java:591)
at
org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configureIncrementalLoad(HFileOutputFormat2.java:441)
at
org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configureIncrementalLoad(HFileOutputFormat2.java:406)
at
org.apache.hadoop.hbase.mapreduce.ImportTsv.createSubmittableJob(ImportTsv.java:555)
at org.apache.hadoop.hbase.mapreduce.ImportTsv.run(ImportTsv.java:763)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.hbase.mapreduce.ImportTsv.main(ImportTsv.java:772)
{noformat}
{{hbase.fs.tmp.dir}} is set to a default value in hbase-default.xml.
I found that hbase configuration resources from its xml are not loaded into
conf object.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14069) Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm
[ https://issues.apache.org/jira/browse/HBASE-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhilash updated HBASE-14069: - Attachment: 0001-Improve-RegionSplitter-v1.patch Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm -- Key: HBASE-14069 URL: https://issues.apache.org/jira/browse/HBASE-14069 Project: HBase Issue Type: New Feature Components: hbase, util Reporter: Elliott Clark Assignee: Abhilash Attachments: 0001-Improve-RegionSplitter-v1.patch, 0001-Improve-RegionSplitter.patch RegionSplittler is the utility that can rolling split regions. It would be nice to be able to split regions and have the normal split points get computed for me so that I'm not reliant on knowing data distribution. Tested manually on standalone mode for various test cases. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14105) Add shell tests for Snapshot
[ https://issues.apache.org/jira/browse/HBASE-14105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singhi updated HBASE-14105: -- Attachment: HBASE-14105-0.98.patch HBASE-14105-branch-1.0.patch Add shell tests for Snapshot Key: HBASE-14105 URL: https://issues.apache.org/jira/browse/HBASE-14105 Project: HBase Issue Type: Sub-task Components: test Reporter: Ashish Singhi Assignee: Ashish Singhi Fix For: 2.0.0, 0.98.14, 1.0.2, 1.2.0, 1.1.2, 1.3.0 Attachments: HBASE-14105-0.98.patch, HBASE-14105-branch-1.0.patch, HBASE-14105.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14024) ImportTsv is not loading hbase-default.xml
[
https://issues.apache.org/jira/browse/HBASE-14024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Singhi updated HBASE-14024:
--
Attachment: HBASE-14024(2) .patch
Retry again.
ImportTsv is not loading hbase-default.xml
--
Key: HBASE-14024
URL: https://issues.apache.org/jira/browse/HBASE-14024
Project: HBase
Issue Type: Bug
Components: mapreduce
Affects Versions: 2.0.0
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Priority: Critical
Fix For: 2.0.0
Attachments: HBASE-14024(1).patch, HBASE-14024(2) .patch,
HBASE-14024.patch
ImportTsv job is failing with below exception
{noformat}
Exception in thread main java.lang.IllegalArgumentException: Can not create
a Path from a null string
at org.apache.hadoop.fs.Path.checkPathArg(Path.java:123)
at org.apache.hadoop.fs.Path.init(Path.java:135)
at org.apache.hadoop.fs.Path.init(Path.java:89)
at
org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configurePartitioner(HFileOutputFormat2.java:591)
at
org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configureIncrementalLoad(HFileOutputFormat2.java:441)
at
org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configureIncrementalLoad(HFileOutputFormat2.java:406)
at
org.apache.hadoop.hbase.mapreduce.ImportTsv.createSubmittableJob(ImportTsv.java:555)
at org.apache.hadoop.hbase.mapreduce.ImportTsv.run(ImportTsv.java:763)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.hbase.mapreduce.ImportTsv.main(ImportTsv.java:772)
{noformat}
{{hbase.fs.tmp.dir}} is set to a default value in hbase-default.xml.
I found that hbase configuration resources from its xml are not loaded into
conf object.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14024) ImportTsv is not loading hbase-default.xml
[
https://issues.apache.org/jira/browse/HBASE-14024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640887#comment-14640887
]
Jerry He commented on HBASE-14024:
--
Looks good.
+1
ImportTsv is not loading hbase-default.xml
--
Key: HBASE-14024
URL: https://issues.apache.org/jira/browse/HBASE-14024
Project: HBase
Issue Type: Bug
Components: mapreduce
Affects Versions: 2.0.0
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Priority: Critical
Fix For: 2.0.0
Attachments: HBASE-14024(1).patch, HBASE-14024(2) .patch,
HBASE-14024.patch
ImportTsv job is failing with below exception
{noformat}
Exception in thread main java.lang.IllegalArgumentException: Can not create
a Path from a null string
at org.apache.hadoop.fs.Path.checkPathArg(Path.java:123)
at org.apache.hadoop.fs.Path.init(Path.java:135)
at org.apache.hadoop.fs.Path.init(Path.java:89)
at
org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configurePartitioner(HFileOutputFormat2.java:591)
at
org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configureIncrementalLoad(HFileOutputFormat2.java:441)
at
org.apache.hadoop.hbase.mapreduce.HFileOutputFormat2.configureIncrementalLoad(HFileOutputFormat2.java:406)
at
org.apache.hadoop.hbase.mapreduce.ImportTsv.createSubmittableJob(ImportTsv.java:555)
at org.apache.hadoop.hbase.mapreduce.ImportTsv.run(ImportTsv.java:763)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.hbase.mapreduce.ImportTsv.main(ImportTsv.java:772)
{noformat}
{{hbase.fs.tmp.dir}} is set to a default value in hbase-default.xml.
I found that hbase configuration resources from its xml are not loaded into
conf object.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14148) Web UI Framable Page
[
https://issues.apache.org/jira/browse/HBASE-14148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641202#comment-14641202
]
Hadoop QA commented on HBASE-14148:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12747096/HBASE-14148-v3-master.patch
against master branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12747096
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1 release
audit warnings (more than the master's current 0 warnings).
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-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):
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14887//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14887//artifact/patchprocess/patchReleaseAuditWarnings.txt
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14887//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14887//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14887//console
This message is automatically generated.
Web UI Framable Page
Key: HBASE-14148
URL: https://issues.apache.org/jira/browse/HBASE-14148
Project: HBase
Issue Type: Bug
Reporter: Apekshit Sharma
Assignee: Apekshit Sharma
Attachments: HBASE-14148-master.patch, HBASE-14148-v2-master.patch,
HBASE-14148-v3-master.patch
The web UIs do not include the X-Frame-Options header to prevent the pages
from being framed from another site.
Reference:
https://www.owasp.org/index.php/Clickjacking
https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet
https://developer.mozilla.org/en-US/docs/Web/HTTP/X-Frame-Options
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13992) Integrate SparkOnHBase into HBase
[ https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641228#comment-14641228 ] Sean Busbey commented on HBASE-13992: - v10 passes for me locally now. It looks like both of the failure cases are checking for SparkException. Could we check directly for TableNotFoundException and NoSuchColumnFamilyException? Integrate SparkOnHBase into HBase - Key: HBASE-13992 URL: https://issues.apache.org/jira/browse/HBASE-13992 Project: HBase Issue Type: New Feature Components: spark Reporter: Ted Malaska Assignee: Ted Malaska Fix For: 2.0.0 Attachments: HBASE-13992.10.patch, HBASE-13992.5.patch, HBASE-13992.6.patch, HBASE-13992.7.patch, HBASE-13992.8.patch, HBASE-13992.9.patch, HBASE-13992.patch, HBASE-13992.patch.3, HBASE-13992.patch.4, HBASE-13992.patch.5 This Jira is to ask if SparkOnHBase can find a home in side HBase core. Here is the github: https://github.com/cloudera-labs/SparkOnHBase I am the core author of this project and the license is Apache 2.0 A blog explaining this project is here http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ A spark Streaming example is here http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/ A real customer using this in produce is blogged here http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/ Please debate and let me know what I can do to make this happen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12751) Allow RowLock to be reader writer
[ https://issues.apache.org/jira/browse/HBASE-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliott Clark updated HBASE-12751: -- Attachment: HBASE-12751-v17.patch Allow RowLock to be reader writer - Key: HBASE-12751 URL: https://issues.apache.org/jira/browse/HBASE-12751 Project: HBase Issue Type: Bug Components: regionserver Affects Versions: 2.0.0, 1.3.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.3.0 Attachments: HBASE-12751-v1.patch, HBASE-12751-v10.patch, HBASE-12751-v10.patch, HBASE-12751-v11.patch, HBASE-12751-v12.patch, HBASE-12751-v13.patch, HBASE-12751-v14.patch, HBASE-12751-v15.patch, HBASE-12751-v16.patch, HBASE-12751-v17.patch, HBASE-12751-v2.patch, HBASE-12751-v3.patch, HBASE-12751-v4.patch, HBASE-12751-v5.patch, HBASE-12751-v6.patch, HBASE-12751-v7.patch, HBASE-12751-v8.patch, HBASE-12751-v9.patch, HBASE-12751.patch Right now every write operation grabs a row lock. This is to prevent values from changing during a read modify write operation (increment or check and put). However it limits parallelism in several different scenarios. If there are several puts to the same row but different columns or stores then this is very limiting. If there are puts to the same column then mvcc number should ensure a consistent ordering. So locking is not needed. However locking for check and put or increment is still needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14148) Web UI Framable Page
[ https://issues.apache.org/jira/browse/HBASE-14148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641236#comment-14641236 ] Sean Busbey commented on HBASE-14148: - err. make that v2 and v3. :) Web UI Framable Page Key: HBASE-14148 URL: https://issues.apache.org/jira/browse/HBASE-14148 Project: HBase Issue Type: Bug Reporter: Apekshit Sharma Assignee: Apekshit Sharma Attachments: HBASE-14148-master.patch, HBASE-14148-v2-master.patch, HBASE-14148-v3-master.patch The web UIs do not include the X-Frame-Options header to prevent the pages from being framed from another site. Reference: https://www.owasp.org/index.php/Clickjacking https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet https://developer.mozilla.org/en-US/docs/Web/HTTP/X-Frame-Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14148) Web UI Framable Page
[ https://issues.apache.org/jira/browse/HBASE-14148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641234#comment-14641234 ] Sean Busbey commented on HBASE-14148: - [~appy] could you give a brief description of the difference between v3 and v4? Web UI Framable Page Key: HBASE-14148 URL: https://issues.apache.org/jira/browse/HBASE-14148 Project: HBase Issue Type: Bug Reporter: Apekshit Sharma Assignee: Apekshit Sharma Attachments: HBASE-14148-master.patch, HBASE-14148-v2-master.patch, HBASE-14148-v3-master.patch The web UIs do not include the X-Frame-Options header to prevent the pages from being framed from another site. Reference: https://www.owasp.org/index.php/Clickjacking https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet https://developer.mozilla.org/en-US/docs/Web/HTTP/X-Frame-Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14057) HBase shell user_permission should list super users defined on hbase-site.xml
[
https://issues.apache.org/jira/browse/HBASE-14057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640934#comment-14640934
]
Matteo Bertozzi commented on HBASE-14057:
-
+1
HBase shell user_permission should list super users defined on hbase-site.xml
-
Key: HBASE-14057
URL: https://issues.apache.org/jira/browse/HBASE-14057
Project: HBase
Issue Type: Task
Components: shell
Affects Versions: 1.0.1
Reporter: Wellington Chevreuil
Assignee: Srikanth Srungarapu
Priority: Minor
Attachments: HBASE-14057-branch-1.patch
On HBase Shell, user_permission command without specifying any user lists all
users granted global permissions (grant 'user', 'RWXCA'):
{noformat}
hbase(main):008:0* user_permission
User
Namespace,Table,Family,Qualifier:Permission
@hbase-admin hbase,hbase:acl,,:
[Permission: actions=READ,WRITE,EXEC,CREATE,ADMIN]
1 row(s) in 3.1710 seconds
{noformat}
Users defined as super users on hbase-site.xml configuration file are not
listed by this same command, even though a super user has the same
permissions/privileges as those defined through grant 'user', 'RWXCA'
command on the shell:
{noformat}
property
namehbase.superuser/name
valuehbase-user/value
/property
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-14148) Web UI Framable Page
[ https://issues.apache.org/jira/browse/HBASE-14148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apekshit Sharma updated HBASE-14148: Attachment: HBASE-14148-v3-master.patch Web UI Framable Page Key: HBASE-14148 URL: https://issues.apache.org/jira/browse/HBASE-14148 Project: HBase Issue Type: Bug Reporter: Apekshit Sharma Assignee: Apekshit Sharma Attachments: HBASE-14148-master.patch, HBASE-14148-v2-master.patch, HBASE-14148-v3-master.patch The web UIs do not include the X-Frame-Options header to prevent the pages from being framed from another site. Reference: https://www.owasp.org/index.php/Clickjacking https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet https://developer.mozilla.org/en-US/docs/Web/HTTP/X-Frame-Options -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14148) Web UI Framable Page
[
https://issues.apache.org/jira/browse/HBASE-14148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641279#comment-14641279
]
Apekshit Sharma commented on HBASE-14148:
-
In v2, license in the start of XFrameOptionsFilter.java was
{noformat}
/**
* Software published by the Open Web Application Security Project
(http://www.owasp.org)
* This software is licensed under the new BSD license.
* Copyright 2009, Jeff Williams a
href=http://www.aspectsecurity.com;Aspect Security/a
*/
{noformat}
I thought -1 release audit was because of that, so I changed it to full
license in V3. Alas, QA is still cribbing. What should I do [~busbey]? Or is it
supposed to be like that?
Web UI Framable Page
Key: HBASE-14148
URL: https://issues.apache.org/jira/browse/HBASE-14148
Project: HBase
Issue Type: Bug
Reporter: Apekshit Sharma
Assignee: Apekshit Sharma
Attachments: HBASE-14148-master.patch, HBASE-14148-v2-master.patch,
HBASE-14148-v3-master.patch
The web UIs do not include the X-Frame-Options header to prevent the pages
from being framed from another site.
Reference:
https://www.owasp.org/index.php/Clickjacking
https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet
https://developer.mozilla.org/en-US/docs/Web/HTTP/X-Frame-Options
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13089) Fix test compilation error on building against htrace-3.2.0-incubating
[
https://issues.apache.org/jira/browse/HBASE-13089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641367#comment-14641367
]
Hadoop QA commented on HBASE-13089:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12747137/HBASE-13089.patch
against master branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12747137
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 4 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{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 post-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 2 zombie test(s):
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14890//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14890//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14890//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14890//console
This message is automatically generated.
Fix test compilation error on building against htrace-3.2.0-incubating
--
Key: HBASE-13089
URL: https://issues.apache.org/jira/browse/HBASE-13089
Project: HBase
Issue Type: Task
Reporter: Masatake Iwasaki
Assignee: Masatake Iwasaki
Priority: Minor
Attachments: HBASE-13089.patch
Test compilation fails if you use htrace-3.2.0 because Span.ROOT_SPAN_ID is
removed. It is used in TestHTraceHooks and should be should be replaced on
the next bumping of htrace version. This is not problem as far as
htrace-3.1.0 is used.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13992) Integrate SparkOnHBase into HBase
[ https://issues.apache.org/jira/browse/HBASE-13992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Malaska updated HBASE-13992: Attachment: HBASE-13992.11.patch Fixed the failure tests to be more pointed. The bad column now checks for a null cell The bad table looks for a HBase client exception and not a SparkException Integrate SparkOnHBase into HBase - Key: HBASE-13992 URL: https://issues.apache.org/jira/browse/HBASE-13992 Project: HBase Issue Type: New Feature Components: spark Reporter: Ted Malaska Assignee: Ted Malaska Fix For: 2.0.0 Attachments: HBASE-13992.10.patch, HBASE-13992.11.patch, HBASE-13992.5.patch, HBASE-13992.6.patch, HBASE-13992.7.patch, HBASE-13992.8.patch, HBASE-13992.9.patch, HBASE-13992.patch, HBASE-13992.patch.3, HBASE-13992.patch.4, HBASE-13992.patch.5 This Jira is to ask if SparkOnHBase can find a home in side HBase core. Here is the github: https://github.com/cloudera-labs/SparkOnHBase I am the core author of this project and the license is Apache 2.0 A blog explaining this project is here http://blog.cloudera.com/blog/2014/12/new-in-cloudera-labs-sparkonhbase/ A spark Streaming example is here http://blog.cloudera.com/blog/2014/11/how-to-do-near-real-time-sessionization-with-spark-streaming-and-apache-hadoop/ A real customer using this in produce is blogged here http://blog.cloudera.com/blog/2015/03/how-edmunds-com-used-spark-streaming-to-build-a-near-real-time-dashboard/ Please debate and let me know what I can do to make this happen. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HBASE-14128) Fix inability to run Multiple MR over the same Snapshot
[
https://issues.apache.org/jira/browse/HBASE-14128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
santosh kumar reassigned HBASE-14128:
-
Assignee: santosh kumar
Fix inability to run Multiple MR over the same Snapshot
---
Key: HBASE-14128
URL: https://issues.apache.org/jira/browse/HBASE-14128
Project: HBase
Issue Type: Bug
Components: mapreduce, snapshots
Reporter: Matteo Bertozzi
Assignee: santosh kumar
Priority: Minor
Labels: beginner, noob
from the list, running multiple MR over the same snapshot does not work
{code}
public static void copySnapshotForScanner(Configuration conf, FileSystem ..
RestoreSnapshotHelper helper = new RestoreSnapshotHelper(conf, fs,
manifest, manifest.getTableDescriptor(), restoreDir, monitor, status);
{code}
the problem is that manifest.getTableDescriptor() will try to clone the
snapshot with the same target name. ending up in file already exist
exceptions.
we just need to clone that descriptor and generate a new target table name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14063) Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
[
https://issues.apache.org/jira/browse/HBASE-14063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640429#comment-14640429
]
Hadoop QA commented on HBASE-14063:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746995/HBASE-14063_3.patch
against master branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12746995
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 7 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
1869 checkstyle errors (more than the master's current 1866 errors).
{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 post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.master.procedure.TestWALProcedureStoreOnHDFS
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14882//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14882//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14882//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14882//console
This message is automatically generated.
Use BufferBackedCell in read path after HBASE-12213 and HBASE-12295
---
Key: HBASE-14063
URL: https://issues.apache.org/jira/browse/HBASE-14063
Project: HBase
Issue Type: Sub-task
Components: regionserver, Scanners
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Fix For: 2.0.0
Attachments: HBASE-14063.patch, HBASE-14063_1.patch,
HBASE-14063_3.patch
Subtask to ensure that the BytebufferBackedCell gets used in the read path
after HBASE-12213 and HBASE-12295 goes in. This would help to clearly change
the required places and makes the review easier.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[
https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640454#comment-14640454
]
Hadoop QA commented on HBASE-14152:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12746996/HBASE-14152-V3.patch
against master branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12746996
{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 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{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 post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.mapreduce.TestImportExport
org.apache.hadoop.hbase.util.TestProcessBasedCluster
{color:red}-1 core zombie tests{color}. There are 2 zombie test(s):
at
org.apache.activemq.broker.policy.DeadLetterTestSupport.testTransientTopicMessage(DeadLetterTestSupport.java:170)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14883//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14883//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14883//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14883//console
This message is automatically generated.
Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
-
Key: HBASE-14152
URL: https://issues.apache.org/jira/browse/HBASE-14152
Project: HBase
Issue Type: Improvement
Components: mob
Affects Versions: 2.0.0
Reporter: Jingcheng Du
Assignee: Jingcheng Du
Fix For: 2.0.0
Attachments: HBASE-14152-V2.patch, HBASE-14152-V3.patch,
HBASE-14152.patch
There are some new warnings in Checkstyle and FindBugs brought in by merging
the feature branch hbase-11339 to trunk.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13089) Fix test compilation error on building against htrace-3.2.0-incubating
[ https://issues.apache.org/jira/browse/HBASE-13089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Esteban Gutierrez updated HBASE-13089: -- Attachment: HBASE-13089.patch Once we bump the version to Hadoop 2.8 or Hadoop 3.0 we should revisit this after HADOOP-11894 got committed. For now I think the fix is ok for practical purposes of the test. Fix test compilation error on building against htrace-3.2.0-incubating -- Key: HBASE-13089 URL: https://issues.apache.org/jira/browse/HBASE-13089 Project: HBase Issue Type: Task Reporter: Masatake Iwasaki Assignee: Masatake Iwasaki Priority: Minor Attachments: HBASE-13089.patch Test compilation fails if you use htrace-3.2.0 because Span.ROOT_SPAN_ID is removed. It is used in TestHTraceHooks and should be should be replaced on the next bumping of htrace version. This is not problem as far as htrace-3.1.0 is used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13089) Fix test compilation error on building against htrace-3.2.0-incubating
[ https://issues.apache.org/jira/browse/HBASE-13089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Esteban Gutierrez updated HBASE-13089: -- Status: Patch Available (was: Open) Fix test compilation error on building against htrace-3.2.0-incubating -- Key: HBASE-13089 URL: https://issues.apache.org/jira/browse/HBASE-13089 Project: HBase Issue Type: Task Reporter: Masatake Iwasaki Assignee: Masatake Iwasaki Priority: Minor Attachments: HBASE-13089.patch Test compilation fails if you use htrace-3.2.0 because Span.ROOT_SPAN_ID is removed. It is used in TestHTraceHooks and should be should be replaced on the next bumping of htrace version. This is not problem as far as htrace-3.1.0 is used. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12751) Allow RowLock to be reader writer
[
https://issues.apache.org/jira/browse/HBASE-12751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641350#comment-14641350
]
Hadoop QA commented on HBASE-12751:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12747127/HBASE-12751-v17.patch
against master branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12747127
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 106
new or modified tests.
{color:red}-1 Anti-pattern{color}. The patch appears to
have anti-pattern where BYTES_COMPARATOR was omitted:
getRegionInfo(), -1, new TreeMapbyte[], ListPath());.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:red}-1 javac{color}. The applied patch generated 25 javac compiler
warnings (more than the master's current 24 warnings).
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 4
warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
1885 checkstyle errors (more than the master's current 1866 errors).
{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:
+this.htableDescriptor.getTableName(),
WALKey.NO_SEQUENCE_ID, nonceGroup, nonce, mvcc);
+ public HLogKey(final byte[] encodedRegionName, final TableName tablename,
final long now, MultiVersionConsistencyControl mvcc) {
+ final long now, ListUUID clusterIds, long nonceGroup, long nonce,
MultiVersionConsistencyControl mvcc) {
+ long logSeqNum, final long now, ListUUID clusterIds, long nonceGroup,
long nonce, MultiVersionConsistencyControl mvcc) {
+ public WALKey(final byte[] encodedRegionName, final TableName tablename,
final long now, MultiVersionConsistencyControl mvcc) {
+ long logSeqNum, final long now, ListUUID clusterIds, long nonceGroup,
long nonce, MultiVersionConsistencyControl mvcc) {
+ long txid = log.append(htd, hri, new WALKey(hri.getEncodedNameAsBytes(),
hri.getTable(), now, mvcc),
+new WALKey(info.getEncodedNameAsBytes(), htd.getTableName(),
System.currentTimeMillis(), mvcc),
+new WALKey(hri.getEncodedNameAsBytes(), htd.getTableName(),
System.currentTimeMillis(), mvcc),
+final WALKey logkey = new WALKey(hri.getEncodedNameAsBytes(),
hri.getTable(), now, mvcc);
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestRegionReplicaFailover
org.apache.hadoop.hbase.regionserver.TestPerColumnFamilyFlush
{color:red}-1 core zombie tests{color}. There are 7 zombie test(s):
at
org.apache.hadoop.hbase.security.visibility.TestVisibilityLabelsWithDefaultVisLabelService.testAddLabels(TestVisibilityLabelsWithDefaultVisLabelService.java:110)
at
org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat2.testWritingPEData(TestHFileOutputFormat2.java:335)
at
org.apache.hadoop.hbase.mapreduce.TestHFileOutputFormat.testMRIncrementalLoad(TestHFileOutputFormat.java:378)
at
org.apache.hadoop.hbase.mapreduce.TestTableInputFormatScanBase.testScan(TestTableInputFormatScanBase.java:243)
at
org.apache.hadoop.hbase.mapreduce.TestTableInputFormatScan1.testScanEmptyToEmpty(TestTableInputFormatScan1.java:45)
at
org.apache.hadoop.hbase.mapreduce.TestCellCounter.testCellCounteEndTimeRange(TestCellCounter.java:179)
at
org.apache.hadoop.hbase.mapreduce.MultiTableInputFormatTestBase.testScan(MultiTableInputFormatTestBase.java:255)
at
org.apache.hadoop.hbase.mapreduce.MultiTableInputFormatTestBase.testScanEmptyToEmpty(MultiTableInputFormatTestBase.java:196)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14889//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14889//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14889//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
[jira] [Commented] (HBASE-14148) Web UI Framable Page
[
https://issues.apache.org/jira/browse/HBASE-14148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641288#comment-14641288
]
Sean Busbey commented on HBASE-14148:
-
you're correct about what's causing the audit failure. it either isn't
detecting that as the BSD license, or it doesn't recognize the BSD license as
legit. We could rephrase the license or configure rat to recognize it, but
let's step back for a minute to address [~eclark]'s concerns.
(Elliot, please correct me if I misstate your position)
{quote}
bq. I don't think that this is complex enough that we should be copying code
from others.
I agree with you that it is very trivial piece of code and that anyone would
have written same. However, when i was reading on clickjacking, i came across
it, read it and it was in the back of my head when I was doing changes. So the
fact remains, that i referenced it and since the code looks same (it couldn't
have looked different, right!), I'd would prefer to have the new-BSD license
here. We all are anyways interested in the feature, right?
{quote}
I don't read any opposition to the feature in Elliot's response, just an
opposition to not doing our own implementation. Is it possible for you to
reimplement the configurable x-frame headers in a way that does not look like
the OWAS version? If it isn't, we'll need to find a contributor who can
reimplement this knowing only the spec (that is, someone who hasn't seen the
OWAS code).
Web UI Framable Page
Key: HBASE-14148
URL: https://issues.apache.org/jira/browse/HBASE-14148
Project: HBase
Issue Type: Bug
Reporter: Apekshit Sharma
Assignee: Apekshit Sharma
Attachments: HBASE-14148-master.patch, HBASE-14148-v2-master.patch,
HBASE-14148-v3-master.patch
The web UIs do not include the X-Frame-Options header to prevent the pages
from being framed from another site.
Reference:
https://www.owasp.org/index.php/Clickjacking
https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet
https://developer.mozilla.org/en-US/docs/Web/HTTP/X-Frame-Options
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14069) Add the ability for RegionSplitter to rolling split without using a SplitAlgorithm
[
https://issues.apache.org/jira/browse/HBASE-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641294#comment-14641294
]
Hadoop QA commented on HBASE-14069:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12747108/0001-Improve-RegionSplitter-v1.patch
against master branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821.
ATTACHMENT ID: 12747108
{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 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
1869 checkstyle errors (more than the master's current 1866 errors).
{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 post-site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.master.procedure.TestMasterFailoverWithProcedures
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at
org.apache.hadoop.hbase.coprocessor.TestOpenTableInCoprocessor.testCoprocessorCanCreateConnectionToRemoteTableWithCustomPool(TestOpenTableInCoprocessor.java:145)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14888//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14888//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14888//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14888//console
This message is automatically generated.
Add the ability for RegionSplitter to rolling split without using a
SplitAlgorithm
--
Key: HBASE-14069
URL: https://issues.apache.org/jira/browse/HBASE-14069
Project: HBase
Issue Type: New Feature
Components: hbase, util
Reporter: Elliott Clark
Assignee: Abhilash
Attachments: 0001-Improve-RegionSplitter-v1.patch,
0001-Improve-RegionSplitter.patch
RegionSplittler is the utility that can rolling split regions. It would be
nice to be able to split regions and have the normal split points get
computed for me so that I'm not reliant on knowing data distribution.
Tested manually on standalone mode for various test cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14070) Hybrid Logical Clocks for HBase
[ https://issues.apache.org/jira/browse/HBASE-14070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14641376#comment-14641376 ] Enis Soztutar commented on HBASE-14070: --- bq. I put a comment in the doc asking how time and sequenceid relate. If time were by region rather than by regionserver, HLC time could be the sequenceid as I see it. Agreed that it will be a nice way of simplification. We are a multi-value database with client settable timestamps and ordering is timestamp-first then seqId. If we want to merge these, it should not be client settable and replication cannot work the way it does today. Current proposal does not propose that we change the HBase semantics at that level. But it also does not prevent it in any way if we want to follow that approach. Once core HLC classes are there, it should be much easy to build. bq. This implies Cell is no longer standalone. It needs a context so its timestamp is interpreted appropriately. True. You can still get the 64-bit timestamp from Cell without Timestamp class. Only if you want to interpret it as wall clock time, you need Timestamp class. Hybrid Logical Clocks for HBase --- Key: HBASE-14070 URL: https://issues.apache.org/jira/browse/HBASE-14070 Project: HBase Issue Type: New Feature Reporter: Enis Soztutar Assignee: Enis Soztutar Attachments: HybridLogicalClocksforHBaseandPhoenix.docx, HybridLogicalClocksforHBaseandPhoenix.pdf HBase and Phoenix uses systems physical clock (PT) to give timestamps to events (read and writes). This works mostly when the system clock is strictly monotonically increasing and there is no cross-dependency between servers clocks. However we know that leap seconds, general clock skew and clock drift are in fact real. This jira proposes using Hybrid Logical Clocks (HLC) as an implementation of hybrid physical clock + a logical clock. HLC is best of both worlds where it keeps causality relationship similar to logical clocks, but still is compatible with NTP based physical system clock. HLC can be represented in 64bits. A design document is attached and also can be found here: https://docs.google.com/document/d/1LL2GAodiYi0waBz5ODGL4LDT4e_bXy8P9h6kWC05Bhw/edit# -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingcheng Du updated HBASE-14152: - Status: Open (was: Patch Available) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152-V3.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jingcheng Du updated HBASE-14152: - Status: Patch Available (was: Open) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152-V3.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640341#comment-14640341 ] Jingcheng Du commented on HBASE-14152: -- Re-submit the patch to trigger the hadoop QA. Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152-V3.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-14152) Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339
[ https://issues.apache.org/jira/browse/HBASE-14152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14640340#comment-14640340 ] Jingcheng Du commented on HBASE-14152: -- The test failure of TestWALProcedureStoreOnHDFS should not be related with this patch. Fix the warnings in Checkstyle and FindBugs brought in by merging hbase-11339 - Key: HBASE-14152 URL: https://issues.apache.org/jira/browse/HBASE-14152 Project: HBase Issue Type: Improvement Components: mob Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: 2.0.0 Attachments: HBASE-14152-V2.patch, HBASE-14152-V3.patch, HBASE-14152.patch There are some new warnings in Checkstyle and FindBugs brought in by merging the feature branch hbase-11339 to trunk. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
