[jira] [Commented] (HBASE-12281) ClonedPrefixTreeCell should implement HeapSize
[ https://issues.apache.org/jira/browse/HBASE-12281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178008#comment-14178008 ] ramkrishna.s.vasudevan commented on HBASE-12281: [~anoop.hbase] Fine with the patch? ClonedPrefixTreeCell should implement HeapSize -- Key: HBASE-12281 URL: https://issues.apache.org/jira/browse/HBASE-12281 Project: HBase Issue Type: Bug Affects Versions: 0.99.1 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0, 0.99.2 Attachments: HBASE-12281.patch, HBASE-12281_1.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12286) [shell] Add server/cluster online load of configuration changes
[ https://issues.apache.org/jira/browse/HBASE-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178011#comment-14178011 ] Manukranth Kolloju commented on HBASE-12286: [~stack], thanks for reviewing it closely. [shell] Add server/cluster online load of configuration changes --- Key: HBASE-12286 URL: https://issues.apache.org/jira/browse/HBASE-12286 Project: HBase Issue Type: New Feature Components: shell Reporter: stack Assignee: Manukranth Kolloju Fix For: 0.99.2 Attachments: 0001-Adding-shell-methods-for-Admin.updateConfiguration.patch, 0001-HBASE-12286-Adding-HBase-Admin-method-for-updating-c.patch Add new loadConfig and loadConfig ServerName verbs to shell to expose new online loading of config changes. This is last piece of a forward port of 0.89fb dynamic config feature done by [~manukranthk] I'll do this last bit if no one else takes it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12286) [shell] Add server/cluster online load of configuration changes
[
https://issues.apache.org/jira/browse/HBASE-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178021#comment-14178021
]
Hadoop QA commented on HBASE-12286:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12676027/0001-HBASE-12286-Adding-HBase-Admin-method-for-updating-c.patch
against trunk revision .
ATTACHMENT ID: 12676027
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{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 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/11412//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11412//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11412//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11412//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11412//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11412//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11412//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11412//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11412//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11412//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11412//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11412//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11412//console
This message is automatically generated.
[shell] Add server/cluster online load of configuration changes
---
Key: HBASE-12286
URL: https://issues.apache.org/jira/browse/HBASE-12286
Project: HBase
Issue Type: New Feature
Components: shell
Reporter: stack
Assignee: Manukranth Kolloju
Fix For: 0.99.2
Attachments:
0001-Adding-shell-methods-for-Admin.updateConfiguration.patch,
0001-HBASE-12286-Adding-HBase-Admin-method-for-updating-c.patch
Add new loadConfig and loadConfig ServerName verbs to shell to expose new
online loading of config changes.
This is last piece of a forward port of 0.89fb dynamic config feature done by
[~manukranthk]
I'll do this last bit if no one else takes it up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-10082) Describe 'table' output is all on one line, could use better formatting
[
https://issues.apache.org/jira/browse/HBASE-10082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178028#comment-14178028
]
Hudson commented on HBASE-10082:
FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #586 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/586/])
HBASE-10082 Describe 'table' output is all on one line, could use better
formatting (Srikanth Srungarapu) (stack: rev
9d7c79790fa2549fb4a3bdbd76bbce44759b1098)
* hbase-shell/src/main/ruby/shell/commands/describe.rb
* hbase-shell/src/main/ruby/hbase/admin.rb
Describe 'table' output is all on one line, could use better formatting
---
Key: HBASE-10082
URL: https://issues.apache.org/jira/browse/HBASE-10082
Project: HBase
Issue Type: Improvement
Components: shell
Environment: 0.94.2-cdh4.2.1
Reporter: Maxime C Dumas
Assignee: Srikanth Srungarapu
Priority: Minor
Fix For: 2.0.0, 0.98.8, 0.99.2
Attachments: HBASE-10082.patch, HBASE-10082_v2.patch,
HBASE-10082_v3.patch, desc_output_screenshot.png
If you describe 'table' from the HBase shell, you get an output like this for
a very simple table:
hbase(main):023:0 describe 'movie'
DESCRIPTION
ENABLED
{NAME = 'movie', FAMILIES = [{NAME = 'info', DATA_BLOCK_ENCODING =
'NONE', B true
LOOMFILTER = 'NONE', REPLICATION_SCOPE = '0', VERSIONS = '3', COMPRESSION
=
'NONE', MIN_VERSIONS = '0', TTL = '2147483647', KEEP_DELETED_CELLS =
'false',
BLOCKSIZE = '65536', IN_MEMORY = 'false', ENCODE_ON_DISK = 'true',
BLOCKCACH
E = 'true'}, {NAME = 'media', DATA_BLOCK_ENCODING = 'NONE', BLOOMFILTER
= 'N
ONE', REPLICATION_SCOPE = '0', VERSIONS = '1', COMPRESSION = 'NONE',
MIN_VERS
IONS = '0', TTL = '2147483647', KEEP_DELETED_CELLS = 'false', BLOCKSIZE
= '6
5536', IN_MEMORY = 'false', ENCODE_ON_DISK = 'true', BLOCKCACHE =
'true'}]}
1 row(s) in 0.0250 seconds
Not only everything is on one row, but also it seems to be limited in width
(82 chars).
I suggest we do a line return on each column family, or format it into a JSON
(lint) format, or anything more readable!
Thanks!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12226) TestAccessController#testPermissionList failing on master
[ https://issues.apache.org/jira/browse/HBASE-12226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178027#comment-14178027 ] Hudson commented on HBASE-12226: FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #586 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/586/]) HBASE-12226 TestAccessController#testPermissionList failing on master (Srikranth Srungarapu) (stack: rev 7130e6b2c2341dde46a0e6a82b7113e716f04aa9) * hbase-server/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessController.java TestAccessController#testPermissionList failing on master - Key: HBASE-12226 URL: https://issues.apache.org/jira/browse/HBASE-12226 Project: HBase Issue Type: Bug Reporter: Andrew Purtell Assignee: Srikanth Srungarapu Fix For: 2.0.0, 0.98.8, 0.99.2 Attachments: HBASE-12226_master.patch TestAccessController#testPermissionList is failing on master with this: https://builds.apache.org/job/HBase-TRUNK/5646/testReport/org.apache.hadoop.hbase.security.access/TestAccessController/testPermissionList/ 2014-10-10 09:00:03,829 WARN [MASTER_TABLE_OPERATIONS-hemera:46872-0] access.AccessController(907): Not adding owner permission for table testPermissionList. hbase:acl is not yet created. AccessController should be configured as the first Coprocessor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12226) TestAccessController#testPermissionList failing on master
[ https://issues.apache.org/jira/browse/HBASE-12226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178034#comment-14178034 ] Hudson commented on HBASE-12226: FAILURE: Integrated in HBase-0.98 #617 (See [https://builds.apache.org/job/HBase-0.98/617/]) HBASE-12226 TestAccessController#testPermissionList failing on master (Srikranth Srungarapu) (stack: rev 7130e6b2c2341dde46a0e6a82b7113e716f04aa9) * hbase-server/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessController.java TestAccessController#testPermissionList failing on master - Key: HBASE-12226 URL: https://issues.apache.org/jira/browse/HBASE-12226 Project: HBase Issue Type: Bug Reporter: Andrew Purtell Assignee: Srikanth Srungarapu Fix For: 2.0.0, 0.98.8, 0.99.2 Attachments: HBASE-12226_master.patch TestAccessController#testPermissionList is failing on master with this: https://builds.apache.org/job/HBase-TRUNK/5646/testReport/org.apache.hadoop.hbase.security.access/TestAccessController/testPermissionList/ 2014-10-10 09:00:03,829 WARN [MASTER_TABLE_OPERATIONS-hemera:46872-0] access.AccessController(907): Not adding owner permission for table testPermissionList. hbase:acl is not yet created. AccessController should be configured as the first Coprocessor -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12304) CellCounter will throw AIOBE when output directory is not specified
Ashish Singhi created HBASE-12304: - Summary: CellCounter will throw AIOBE when output directory is not specified Key: HBASE-12304 URL: https://issues.apache.org/jira/browse/HBASE-12304 Project: HBase Issue Type: Bug Components: mapreduce Affects Versions: 0.98.5 Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor CellCounter will throw ArrayIndexOutOfBoundsException when output directory is not specified instead it should display the usage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12303) Seek to next row after family delete markers
[
https://issues.apache.org/jira/browse/HBASE-12303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178081#comment-14178081
]
Hadoop QA commented on HBASE-12303:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12676030/12303.txt
against trunk revision .
ATTACHMENT ID: 12676030
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{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 site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.regionserver.TestHRegion
org.apache.hadoop.hbase.security.access.TestAccessController
org.apache.hadoop.hbase.util.TestHBaseFsck
org.apache.hadoop.hbase.client.TestScannersFromClientSide
org.apache.hadoop.hbase.client.TestAdmin
org.apache.hadoop.hbase.quotas.TestQuotaThrottle
org.apache.hadoop.hbase.regionserver.TestBlocksRead
org.apache.hadoop.hbase.security.access.TestTablePermissions
{color:red}-1 core zombie tests{color}. There are 5 zombie test(s):
at
org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClient.testRestoreSnapshot(TestRestoreSnapshotFromClient.java:145)
at
org.apache.hadoop.hbase.client.TestCloneSnapshotFromClient.testCloneSnapshot(TestCloneSnapshotFromClient.java:167)
at
org.apache.hadoop.hbase.client.TestCloneSnapshotFromClient.testCloneSnapshot(TestCloneSnapshotFromClient.java:160)
at
org.apache.hadoop.hbase.client.TestCloneSnapshotFromClient.testCloneSnapshot(TestCloneSnapshotFromClient.java:167)
at
org.apache.hadoop.hbase.client.TestCloneSnapshotFromClient.testCloneSnapshot(TestCloneSnapshotFromClient.java:160)
at
org.apache.hadoop.hbase.snapshot.TestRestoreFlushSnapshotFromClient.testRestoreSnapshotOfCloned(TestRestoreFlushSnapshotFromClient.java:194)
at
org.apache.hadoop.hbase.client.TestRestoreSnapshotFromClient.testRestoreSnapshot(TestRestoreSnapshotFromClient.java:145)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11413//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11413//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11413//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11413//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11413//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11413//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11413//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11413//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11413//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11413//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11413//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
[jira] [Updated] (HBASE-12304) CellCounter will throw AIOBE when output directory is not specified
[ https://issues.apache.org/jira/browse/HBASE-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singhi updated HBASE-12304: -- Attachment: HBase-12304.patch Attached patch for master branch. Some one please review. CellCounter will throw AIOBE when output directory is not specified --- Key: HBASE-12304 URL: https://issues.apache.org/jira/browse/HBASE-12304 Project: HBase Issue Type: Bug Components: mapreduce Affects Versions: 0.98.5 Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor Attachments: HBase-12304.patch CellCounter will throw ArrayIndexOutOfBoundsException when output directory is not specified instead it should display the usage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12304) CellCounter will throw AIOBE when output directory is not specified
[ https://issues.apache.org/jira/browse/HBASE-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashish Singhi updated HBASE-12304: -- Status: Patch Available (was: Open) CellCounter will throw AIOBE when output directory is not specified --- Key: HBASE-12304 URL: https://issues.apache.org/jira/browse/HBASE-12304 Project: HBase Issue Type: Bug Components: mapreduce Affects Versions: 0.98.5 Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor Attachments: HBase-12304.patch CellCounter will throw ArrayIndexOutOfBoundsException when output directory is not specified instead it should display the usage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12305) Memstore and MemstoreScanner should work with BBs.
ramkrishna.s.vasudevan created HBASE-12305: -- Summary: Memstore and MemstoreScanner should work with BBs. Key: HBASE-12305 URL: https://issues.apache.org/jira/browse/HBASE-12305 Project: HBase Issue Type: Sub-task Reporter: ramkrishna.s.vasudevan Anoop's work of Memstore as a block would be beneficial here and in that we could ensure that Memstore also works with buffers. This would help in easy comparison of cells from the Readers backed by buffers and the cells in the memstores (currently backed by byte[]). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12304) CellCounter will throw AIOBE when output directory is not specified
[
https://issues.apache.org/jira/browse/HBASE-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178178#comment-14178178
]
Hadoop QA commented on HBASE-12304:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12676049/HBase-12304.patch
against trunk revision .
ATTACHMENT ID: 12676049
{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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{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 site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
{color:red}-1 core zombie tests{color}. There are 1 zombie test(s):
at org.apache.sling.testing.tools.retry.RetryLoop.init(RetryLoop.java:59)
at
org.apache.sling.discovery.impl.cluster.ClusterLoadTest.testFourInstances(ClusterLoadTest.java:100)
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11414//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11414//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11414//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11414//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11414//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11414//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11414//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11414//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11414//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11414//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11414//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11414//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11414//console
This message is automatically generated.
CellCounter will throw AIOBE when output directory is not specified
---
Key: HBASE-12304
URL: https://issues.apache.org/jira/browse/HBASE-12304
Project: HBase
Issue Type: Bug
Components: mapreduce
Affects Versions: 0.98.5
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Priority: Minor
Attachments: HBase-12304.patch
CellCounter will throw ArrayIndexOutOfBoundsException when output directory
is not specified instead it should display the usage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-12306) CellCounter output's wrong value for Total Families Across all Rows in output file
Ashish Singhi created HBASE-12306:
-
Summary: CellCounter output's wrong value for Total Families
Across all Rows in output file
Key: HBASE-12306
URL: https://issues.apache.org/jira/browse/HBASE-12306
Project: HBase
Issue Type: Bug
Components: mapreduce
Affects Versions: 0.98.5
Reporter: Ashish Singhi
Assignee: Ashish Singhi
CellCounter output's wrong value for {{Total Families Across all Rows}} in
output file.
The scan output of table looks like the following
{noformat}
r1 column=f:count,
timestamp=1413444040422, value=v1
r1 column=f1:count1,
timestamp=1413444045493, value=v1
r1 column=f2:count2,
timestamp=1413444051461, value=v1
r2 column=f:count,
timestamp=1413444073282, value=v2
r2 column=f1:count1,
timestamp=1413444077666, value=v2
r2 column=f2:count2,
timestamp=1413444083141, value=v2
r3 column=f:count,
timestamp=1413444184672, value=v3
{noformat}
and the output in the output file of CellCounter looks like this
{noformat}
Total Families Across all Rows 7
Total Qualifiers across all Rows7
Total ROWS 3
f 3
f,count 3
f1 2
f1,count1 2
f2 2
f2,count2 2
r1,f,count_Versions 1
r1,f1,count1_Versions 1
r1,f2,count2_Versions 1
r2,f,count_Versions 1
r2,f1,count1_Versions 1
r2,f2,count2_Versions 1
r3,f,count_Versions 1
{noformat}
The {{Total Families Across all Rows}} should be 3, but it is 7.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11419) After increasing TTL value of a hbase table having pre-split regions and decreasing TTL value, table becomes inaccessible.
[ https://issues.apache.org/jira/browse/HBASE-11419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178203#comment-14178203 ] Prabhu Joseph commented on HBASE-11419: --- STEPS TO REPRODUCE: In a distributed Hbase with two HRegionservers, 1. javac -cp jars needed , hbase jars and hbase-site.xml HBaseExporter.java 2. java -cp jars needed , hbase jars and hbase-site.xml HBaseExporter create [ copy the account.csv to /tmp folder ] java -cp jars needed , hbase jars and hbase-site.xml HBaseExporter import 3. java -cp jars needed , hbase jars and hbase-site.xml HBaseExporter ttl These steps create AccountHistoryMA1 table with 530 regions and import some data in it. TTL value during creation is 180 days (15552000) DATA inserted has some data older than 180 days and the data inserted is still in memstore, not flushed to disk. Step 3 increases the ttl value to 800 days (6912). After this when we scan the table following error thrown, java.lang.IllegalStateException: Block index not loaded On analysis we found there were two hfiles created with empty rows, which are for rowkeys 180 days older. so we suspect Hbase creates hfile first and not writes the data older than TTl value. Workaround: Flush before changing the TTL does not create hfiles with empty rows. After increasing TTL value of a hbase table having pre-split regions and decreasing TTL value, table becomes inaccessible. -- Key: HBASE-11419 URL: https://issues.apache.org/jira/browse/HBASE-11419 Project: HBase Issue Type: Bug Components: HFile Affects Versions: 0.94.6 Environment: Linux x86_64 Reporter: Prabhu Joseph Priority: Blocker Fix For: 0.94.6 Original Estimate: 96h Remaining Estimate: 96h After increasing and decreasing the TTL value of a Hbase Table , table gets inaccessible. Scan table not working. Scan in hbase shell throws java.lang.IllegalStateException: Block index not loaded at com.google.common.base.Preconditions.checkState(Preconditions.java:145) at org.apache.hadoop.hbase.io.hfile.HFileReaderV1.blockContainingKey(HFileReaderV1.java:181) at org.apache.hadoop.hbase.io.hfile.HFileReaderV1$AbstractScannerV1.seekTo(HFileReaderV1.java:426) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:226) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:145) at org.apache.hadoop.hbase.regionserver.StoreScanner.init(StoreScanner.java:131) at org.apache.hadoop.hbase.regionserver.Store.getScanner(Store.java:2015) at org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.init(HRegion.java:3706) at org.apache.hadoop.hbase.regionserver.HRegion.instantiateRegionScanner(HRegion.java:1761) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1753) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1730) at org.apache.hadoop.hbase.regionserver.HRegionServer.openScanner(HRegionServer.java:2409) at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:320) at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1426) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-11419) After increasing TTL value of a hbase table having pre-split regions and decreasing TTL value, table becomes inaccessible.
[ https://issues.apache.org/jira/browse/HBASE-11419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Prabhu Joseph updated HBASE-11419: -- Attachment: HBaseExporter.java account.csv After increasing TTL value of a hbase table having pre-split regions and decreasing TTL value, table becomes inaccessible. -- Key: HBASE-11419 URL: https://issues.apache.org/jira/browse/HBASE-11419 Project: HBase Issue Type: Bug Components: HFile Affects Versions: 0.94.6 Environment: Linux x86_64 Reporter: Prabhu Joseph Priority: Blocker Fix For: 0.94.6 Attachments: HBaseExporter.java, account.csv Original Estimate: 96h Remaining Estimate: 96h After increasing and decreasing the TTL value of a Hbase Table , table gets inaccessible. Scan table not working. Scan in hbase shell throws java.lang.IllegalStateException: Block index not loaded at com.google.common.base.Preconditions.checkState(Preconditions.java:145) at org.apache.hadoop.hbase.io.hfile.HFileReaderV1.blockContainingKey(HFileReaderV1.java:181) at org.apache.hadoop.hbase.io.hfile.HFileReaderV1$AbstractScannerV1.seekTo(HFileReaderV1.java:426) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:226) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:145) at org.apache.hadoop.hbase.regionserver.StoreScanner.init(StoreScanner.java:131) at org.apache.hadoop.hbase.regionserver.Store.getScanner(Store.java:2015) at org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.init(HRegion.java:3706) at org.apache.hadoop.hbase.regionserver.HRegion.instantiateRegionScanner(HRegion.java:1761) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1753) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1730) at org.apache.hadoop.hbase.regionserver.HRegionServer.openScanner(HRegionServer.java:2409) at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:320) at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1426) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12306) CellCounter output's wrong value for Total Families Across all Rows in output file
[
https://issues.apache.org/jira/browse/HBASE-12306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Singhi updated HBASE-12306:
--
Attachment: HBASE-12306.patch
Patch for master branch.
Some one please review.
CellCounter output's wrong value for Total Families Across all Rows in output
file
--
Key: HBASE-12306
URL: https://issues.apache.org/jira/browse/HBASE-12306
Project: HBase
Issue Type: Bug
Components: mapreduce
Affects Versions: 0.98.5
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Attachments: HBASE-12306.patch
CellCounter output's wrong value for {{Total Families Across all Rows}} in
output file.
The scan output of table looks like the following
{noformat}
r1 column=f:count,
timestamp=1413444040422, value=v1
r1 column=f1:count1,
timestamp=1413444045493, value=v1
r1 column=f2:count2,
timestamp=1413444051461, value=v1
r2 column=f:count,
timestamp=1413444073282, value=v2
r2 column=f1:count1,
timestamp=1413444077666, value=v2
r2 column=f2:count2,
timestamp=1413444083141, value=v2
r3 column=f:count,
timestamp=1413444184672, value=v3
{noformat}
and the output in the output file of CellCounter looks like this
{noformat}
Total Families Across all Rows 7
Total Qualifiers across all Rows7
Total ROWS 3
f 3
f,count 3
f1 2
f1,count1 2
f2 2
f2,count2 2
r1,f,count_Versions 1
r1,f1,count1_Versions 1
r1,f2,count2_Versions 1
r2,f,count_Versions 1
r2,f1,count1_Versions 1
r2,f2,count2_Versions 1
r3,f,count_Versions 1
{noformat}
The {{Total Families Across all Rows}} should be 3, but it is 7.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12306) CellCounter output's wrong value for Total Families Across all Rows in output file
[
https://issues.apache.org/jira/browse/HBASE-12306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ashish Singhi updated HBASE-12306:
--
Status: Patch Available (was: Open)
{{Total Families Across all Rows}} will now be incremented only once per family.
CellCounter output's wrong value for Total Families Across all Rows in output
file
--
Key: HBASE-12306
URL: https://issues.apache.org/jira/browse/HBASE-12306
Project: HBase
Issue Type: Bug
Components: mapreduce
Affects Versions: 0.98.5
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Attachments: HBASE-12306.patch
CellCounter output's wrong value for {{Total Families Across all Rows}} in
output file.
The scan output of table looks like the following
{noformat}
r1 column=f:count,
timestamp=1413444040422, value=v1
r1 column=f1:count1,
timestamp=1413444045493, value=v1
r1 column=f2:count2,
timestamp=1413444051461, value=v1
r2 column=f:count,
timestamp=1413444073282, value=v2
r2 column=f1:count1,
timestamp=1413444077666, value=v2
r2 column=f2:count2,
timestamp=1413444083141, value=v2
r3 column=f:count,
timestamp=1413444184672, value=v3
{noformat}
and the output in the output file of CellCounter looks like this
{noformat}
Total Families Across all Rows 7
Total Qualifiers across all Rows7
Total ROWS 3
f 3
f,count 3
f1 2
f1,count1 2
f2 2
f2,count2 2
r1,f,count_Versions 1
r1,f1,count1_Versions 1
r1,f2,count2_Versions 1
r2,f,count_Versions 1
r2,f1,count1_Versions 1
r2,f2,count2_Versions 1
r3,f,count_Versions 1
{noformat}
The {{Total Families Across all Rows}} should be 3, but it is 7.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12304) CellCounter will throw AIOBE when output directory is not specified
[ https://issues.apache.org/jira/browse/HBASE-12304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178217#comment-14178217 ] Ashish Singhi commented on HBASE-12304: --- bq. -1 core zombie tests. There are 1 zombie test(s): at org.apache.sling.testing.tools.retry.RetryLoop.init(RetryLoop.java:59) at org.apache.sling.discovery.impl.cluster.ClusterLoadTest.testFourInstances(ClusterLoadTest.java:100) Failures I don't think it is related to patch. CellCounter will throw AIOBE when output directory is not specified --- Key: HBASE-12304 URL: https://issues.apache.org/jira/browse/HBASE-12304 Project: HBase Issue Type: Bug Components: mapreduce Affects Versions: 0.98.5 Reporter: Ashish Singhi Assignee: Ashish Singhi Priority: Minor Attachments: HBase-12304.patch CellCounter will throw ArrayIndexOutOfBoundsException when output directory is not specified instead it should display the usage. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12281) ClonedPrefixTreeCell should implement HeapSize
[
https://issues.apache.org/jira/browse/HBASE-12281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178234#comment-14178234
]
Anoop Sam John commented on HBASE-12281:
{code}
ListTag tags = Tag.asList(getTagsArray(), getTagsOffset(), getTagsLength());
+ if (tags != null) {
+ListString tagsString = new ArrayListString();
+for (Tag t : tags) {
+ tagsString.add((t.getType()) + : +
Bytes.toStringBinary(t.getValue()));
+}
+ }
{code}
tagsString unused. We dont need to write tags details in toString. Just remove
above code block.
{code}
return FIXED_OVERHEAD + rowLength + famLength + qualLength + valLength +
tagsLength
+ + KeyValue.TIMESTAMP_TYPE_SIZE;
{code}
FIXED_OVERHEAD already includes the long and byte type size corresponding to rs
and type. KeyValue.TIMESTAMP_TYPE_SIZE addition not needed no?
ClonedPrefixTreeCell should implement HeapSize
--
Key: HBASE-12281
URL: https://issues.apache.org/jira/browse/HBASE-12281
Project: HBase
Issue Type: Bug
Affects Versions: 0.99.1
Reporter: ramkrishna.s.vasudevan
Assignee: ramkrishna.s.vasudevan
Fix For: 2.0.0, 0.99.2
Attachments: HBASE-12281.patch, HBASE-12281_1.patch
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (HBASE-12301) user_permission command does not show global permissions
[
https://issues.apache.org/jira/browse/HBASE-12301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Bertozzi reassigned HBASE-12301:
---
Assignee: Matteo Bertozzi
user_permission command does not show global permissions
Key: HBASE-12301
URL: https://issues.apache.org/jira/browse/HBASE-12301
Project: HBase
Issue Type: Bug
Components: security, shell
Affects Versions: 0.98.4, 2.0.0
Reporter: Jerry He
Assignee: Matteo Bertozzi
It seems that since 0,98 or later, the shell command does not show global
permission anymore, even requested by user with the right privilege.
{code}
hbase(main):004:0 user_permission
UserTable,Family,Qualifier:Permission
hbase default,table1,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table1,,: [Permission:
actions=READ,WRITE]
hbase default,table2,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table2,,: [Permission:
actions=READ,WRITE]
{code}
I recall in the older versions, global permissions were shown as permissions
on the hbase:acl table.
Anyway we need a way to show the global permissions as part of
user_permission request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12301) user_permission command does not show global permissions
[
https://issues.apache.org/jira/browse/HBASE-12301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Bertozzi updated HBASE-12301:
Attachment: HBASE-12301-v0.patch
the default user_permission with no argument was now going directly to the
get table permission instead of going to the global one. basically the first if
(tableRegex == null) will never be true.
Then there was another minor issue with the namespace handling, not checking
for the nil tableRegex.
the attached patch changes the behavior to what was before, showing only the
global permission when user_permission is invoked with no argument.
If you want the table permission you have to specify the regex as was described
in the user_permission help
{noformat}
hbase user_permission
hbase user_permission 'table1'
hbase user_permission 'namespace1:table1'
hbase user_permission '.*'
hbase user_permission '^[A-C].*'
{noformat}
user_permission command does not show global permissions
Key: HBASE-12301
URL: https://issues.apache.org/jira/browse/HBASE-12301
Project: HBase
Issue Type: Bug
Components: security, shell
Affects Versions: 0.98.4, 2.0.0
Reporter: Jerry He
Assignee: Matteo Bertozzi
Attachments: HBASE-12301-v0.patch
It seems that since 0,98 or later, the shell command does not show global
permission anymore, even requested by user with the right privilege.
{code}
hbase(main):004:0 user_permission
UserTable,Family,Qualifier:Permission
hbase default,table1,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table1,,: [Permission:
actions=READ,WRITE]
hbase default,table2,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table2,,: [Permission:
actions=READ,WRITE]
{code}
I recall in the older versions, global permissions were shown as permissions
on the hbase:acl table.
Anyway we need a way to show the global permissions as part of
user_permission request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12281) ClonedPrefixTreeCell should implement HeapSize
[ https://issues.apache.org/jira/browse/HBASE-12281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-12281: --- Status: Open (was: Patch Available) ClonedPrefixTreeCell should implement HeapSize -- Key: HBASE-12281 URL: https://issues.apache.org/jira/browse/HBASE-12281 Project: HBase Issue Type: Bug Affects Versions: 0.99.1 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0, 0.99.2 Attachments: HBASE-12281.patch, HBASE-12281_1.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12281) ClonedPrefixTreeCell should implement HeapSize
[ https://issues.apache.org/jira/browse/HBASE-12281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-12281: --- Attachment: HBASE-12281_2.patch Updated patch. The KeyValue.TIMESTAMP_TYPE_SIZE needs to be removed from BufferedDataBlockEncoder.ClonedSeekerState also. Will commit this unless objections. Thanks for the reviews. ClonedPrefixTreeCell should implement HeapSize -- Key: HBASE-12281 URL: https://issues.apache.org/jira/browse/HBASE-12281 Project: HBase Issue Type: Bug Affects Versions: 0.99.1 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0, 0.99.2 Attachments: HBASE-12281.patch, HBASE-12281_1.patch, HBASE-12281_2.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12306) CellCounter output's wrong value for Total Families Across all Rows in output file
[
https://issues.apache.org/jira/browse/HBASE-12306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178286#comment-14178286
]
Hadoop QA commented on HBASE-12306:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12676065/HBASE-12306.patch
against trunk revision .
ATTACHMENT ID: 12676065
{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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{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 site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.mapreduce.TestSecureLoadIncrementalHFilesSplitRecovery
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11415//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11415//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11415//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11415//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11415//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11415//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11415//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11415//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11415//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11415//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11415//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11415//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11415//console
This message is automatically generated.
CellCounter output's wrong value for Total Families Across all Rows in output
file
--
Key: HBASE-12306
URL: https://issues.apache.org/jira/browse/HBASE-12306
Project: HBase
Issue Type: Bug
Components: mapreduce
Affects Versions: 0.98.5
Reporter: Ashish Singhi
Assignee: Ashish Singhi
Attachments: HBASE-12306.patch
CellCounter output's wrong value for {{Total Families Across all Rows}} in
output file.
The scan output of table looks like the following
{noformat}
r1 column=f:count,
timestamp=1413444040422, value=v1
r1 column=f1:count1,
timestamp=1413444045493, value=v1
r1 column=f2:count2,
timestamp=1413444051461, value=v1
r2 column=f:count,
timestamp=1413444073282, value=v2
r2 column=f1:count1,
timestamp=1413444077666, value=v2
r2 column=f2:count2,
timestamp=1413444083141, value=v2
r3 column=f:count,
timestamp=1413444184672, value=v3
{noformat}
and the output in the output file of CellCounter looks like this
{noformat}
Total
[jira] [Commented] (HBASE-12281) ClonedPrefixTreeCell should implement HeapSize
[ https://issues.apache.org/jira/browse/HBASE-12281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178301#comment-14178301 ] Anoop Sam John commented on HBASE-12281: +1 ClonedPrefixTreeCell should implement HeapSize -- Key: HBASE-12281 URL: https://issues.apache.org/jira/browse/HBASE-12281 Project: HBase Issue Type: Bug Affects Versions: 0.99.1 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0, 0.99.2 Attachments: HBASE-12281.patch, HBASE-12281_1.patch, HBASE-12281_2.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12301) user_permission command does not show global permissions
[
https://issues.apache.org/jira/browse/HBASE-12301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178324#comment-14178324
]
Anoop Sam John commented on HBASE-12301:
Patch looks good
+1 if it works with all cases as old way. Thanks Matteo.
user_permission command does not show global permissions
Key: HBASE-12301
URL: https://issues.apache.org/jira/browse/HBASE-12301
Project: HBase
Issue Type: Bug
Components: security, shell
Affects Versions: 0.98.4, 2.0.0
Reporter: Jerry He
Assignee: Matteo Bertozzi
Attachments: HBASE-12301-v0.patch
It seems that since 0,98 or later, the shell command does not show global
permission anymore, even requested by user with the right privilege.
{code}
hbase(main):004:0 user_permission
UserTable,Family,Qualifier:Permission
hbase default,table1,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table1,,: [Permission:
actions=READ,WRITE]
hbase default,table2,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table2,,: [Permission:
actions=READ,WRITE]
{code}
I recall in the older versions, global permissions were shown as permissions
on the hbase:acl table.
Anyway we need a way to show the global permissions as part of
user_permission request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12202) Support DirectByteBuffer usage in HFileBlock
[ https://issues.apache.org/jira/browse/HBASE-12202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-12202: --- Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to 0.99+ Thanks for the reviews Support DirectByteBuffer usage in HFileBlock Key: HBASE-12202 URL: https://issues.apache.org/jira/browse/HBASE-12202 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: Anoop Sam John Assignee: Anoop Sam John Fix For: 2.0.0, 0.99.2 Attachments: HBASE-12202.patch, HBASE-12202_V2.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10713) A MemStore implementation with in memory flushes to CellBlocks
[ https://issues.apache.org/jira/browse/HBASE-10713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-10713: --- Attachment: HBASE-10713_WIP.patch Attaching a WIP patch for ref and early look. Still some more TODOs which I will see once HBASE-11425 is done. A MemStore implementation with in memory flushes to CellBlocks -- Key: HBASE-10713 URL: https://issues.apache.org/jira/browse/HBASE-10713 Project: HBase Issue Type: New Feature Reporter: Anoop Sam John Assignee: Anoop Sam John Fix For: 2.0.0 Attachments: HBASE-10713_WIP.patch After HBASE-10648 we can plugin any implementation for MemStore. This issue aims at coming up with an implementation, in which we will have in between in memory flushes. This will reduce the need to keep lots of KVs in heap as well as in CSLM. CSLM perform poor when no# items in it increases. We can keep create CellBlocks (contigous byte[] like HFile block) out of KVs and keep it as one object rather than many KVs. At some point in time, MemStore might have N CellBlocks and one CSLM. These in memory CellBlocks can be compacted to one bigger block in between. We can target that in follow on tasks once the basic code is ready. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10713) A MemStore implementation with in memory flushes to CellBlocks
[ https://issues.apache.org/jira/browse/HBASE-10713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-10713: --- Attachment: (was: HBASE-10713_WIP.patch) A MemStore implementation with in memory flushes to CellBlocks -- Key: HBASE-10713 URL: https://issues.apache.org/jira/browse/HBASE-10713 Project: HBase Issue Type: New Feature Reporter: Anoop Sam John Assignee: Anoop Sam John Fix For: 2.0.0 After HBASE-10648 we can plugin any implementation for MemStore. This issue aims at coming up with an implementation, in which we will have in between in memory flushes. This will reduce the need to keep lots of KVs in heap as well as in CSLM. CSLM perform poor when no# items in it increases. We can keep create CellBlocks (contigous byte[] like HFile block) out of KVs and keep it as one object rather than many KVs. At some point in time, MemStore might have N CellBlocks and one CSLM. These in memory CellBlocks can be compacted to one bigger block in between. We can target that in follow on tasks once the basic code is ready. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10713) A MemStore implementation with in memory flushes to CellBlocks
[ https://issues.apache.org/jira/browse/HBASE-10713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John updated HBASE-10713: --- Attachment: HBASE-10713_WIP.patch A MemStore implementation with in memory flushes to CellBlocks -- Key: HBASE-10713 URL: https://issues.apache.org/jira/browse/HBASE-10713 Project: HBase Issue Type: New Feature Reporter: Anoop Sam John Assignee: Anoop Sam John Fix For: 2.0.0 Attachments: HBASE-10713_WIP.patch After HBASE-10648 we can plugin any implementation for MemStore. This issue aims at coming up with an implementation, in which we will have in between in memory flushes. This will reduce the need to keep lots of KVs in heap as well as in CSLM. CSLM perform poor when no# items in it increases. We can keep create CellBlocks (contigous byte[] like HFile block) out of KVs and keep it as one object rather than many KVs. At some point in time, MemStore might have N CellBlocks and one CSLM. These in memory CellBlocks can be compacted to one bigger block in between. We can target that in follow on tasks once the basic code is ready. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12293) Tests are logging too much
[ https://issues.apache.org/jira/browse/HBASE-12293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178404#comment-14178404 ] Nicolas Liochon commented on HBASE-12293: - tests should be at info level at the minimum, as in production: if not we will discover in production/integration test that we log too much (or worse triggers NPE or stuff like this). For the same reason, I prefer to use the debug level in tests, to be sure that I won't have surprises (NPE) if I try to use them. What I did in the past is reusing the info from the apache build (run time and logs), and looked at the both the log size and the log rate per test to prioritize the tests I was looking at. Then I was just improving the logs around these area. Tests are logging too much -- Key: HBASE-12293 URL: https://issues.apache.org/jira/browse/HBASE-12293 Project: HBase Issue Type: Bug Components: test Reporter: Dima Spivak Assignee: Dima Spivak Priority: Minor In trying to solve HBASE-12285, it was pointed out that tests are writing too much to output again. At best, this is a sloppy practice and, at worst, it leaves us open to builds breaking when our test tools can't handle the flood. If [~nkeywal] would be willing give me a little bit of mentoring on how he dealt with this problem a few years back, I'd be happy to add it to my plate. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12202) Support DirectByteBuffer usage in HFileBlock
[ https://issues.apache.org/jira/browse/HBASE-12202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178407#comment-14178407 ] Hudson commented on HBASE-12202: FAILURE: Integrated in HBase-1.0 #332 (See [https://builds.apache.org/job/HBase-1.0/332/]) HBASE-12202 Support DirectByteBuffer usage in HFileBlock. (anoopsamjohn: rev 67d1cee2d868d0924968dccfb93b1536a0265086) * hbase-common/src/main/java/org/apache/hadoop/hbase/io/ByteBufferInputStream.java * hbase-common/src/main/java/org/apache/hadoop/hbase/io/encoding/HFileBlockDefaultDecodingContext.java * hbase-common/src/main/java/org/apache/hadoop/hbase/io/encoding/HFileBlockDecodingContext.java * hbase-common/src/test/java/org/apache/hadoop/hbase/io/TestByteBufferInputStream.java * hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/HFileBlock.java * hbase-common/src/main/java/org/apache/hadoop/hbase/io/hfile/BlockType.java * hbase-common/src/main/java/org/apache/hadoop/hbase/util/ByteBufferUtils.java Support DirectByteBuffer usage in HFileBlock Key: HBASE-12202 URL: https://issues.apache.org/jira/browse/HBASE-12202 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: Anoop Sam John Assignee: Anoop Sam John Fix For: 2.0.0, 0.99.2 Attachments: HBASE-12202.patch, HBASE-12202_V2.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12285) Builds are failing, possibly because of SUREFIRE-1091
[ https://issues.apache.org/jira/browse/HBASE-12285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178414#comment-14178414 ] Nicolas Liochon commented on HBASE-12285: - I think changing the log level is not a good idea (I added a comment in the related jira: it's very common to discover NPE when you activate logs, and it's a very bad user experience: something does not work as expected, you activate the debug logs to understand and then you get a NPE.). If we don't want to pay the testing cost of the debug logs, then I'm +1 for removing them (seriously: they are becoming useless as we now run info by default). But if we keep them in the code we must keep them in the tests. Builds are failing, possibly because of SUREFIRE-1091 - Key: HBASE-12285 URL: https://issues.apache.org/jira/browse/HBASE-12285 Project: HBase Issue Type: Bug Affects Versions: 1.0.0 Reporter: Dima Spivak Assignee: Dima Spivak Priority: Blocker Attachments: HBASE-12285_branch-1_v1.patch Our branch-1 builds on builds.apache.org have been failing in recent days after we switched over to an official version of Surefire a few days back (HBASE-4955). The version we're using, 2.17, is hit by a bug ([SUREFIRE-1091|https://jira.codehaus.org/browse/SUREFIRE-1091]) that results in an IOException, which looks like what we're seeing on Jenkins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12202) Support DirectByteBuffer usage in HFileBlock
[ https://issues.apache.org/jira/browse/HBASE-12202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178451#comment-14178451 ] Hudson commented on HBASE-12202: SUCCESS: Integrated in HBase-TRUNK #5678 (See [https://builds.apache.org/job/HBase-TRUNK/5678/]) HBASE-12202 Support DirectByteBuffer usage in HFileBlock. (anoopsamjohn: rev c01d9981d89ba3633377952d132c88536c86ebc5) * hbase-common/src/main/java/org/apache/hadoop/hbase/io/encoding/HFileBlockDecodingContext.java * hbase-common/src/main/java/org/apache/hadoop/hbase/util/ByteBufferUtils.java * hbase-common/src/main/java/org/apache/hadoop/hbase/io/encoding/HFileBlockDefaultDecodingContext.java * hbase-common/src/main/java/org/apache/hadoop/hbase/io/ByteBufferInputStream.java * hbase-server/src/main/java/org/apache/hadoop/hbase/io/hfile/HFileBlock.java * hbase-common/src/test/java/org/apache/hadoop/hbase/io/TestByteBufferInputStream.java * hbase-common/src/main/java/org/apache/hadoop/hbase/io/hfile/BlockType.java Support DirectByteBuffer usage in HFileBlock Key: HBASE-12202 URL: https://issues.apache.org/jira/browse/HBASE-12202 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Reporter: Anoop Sam John Assignee: Anoop Sam John Fix For: 2.0.0, 0.99.2 Attachments: HBASE-12202.patch, HBASE-12202_V2.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12285) Builds are failing, possibly because of SUREFIRE-1091
[ https://issues.apache.org/jira/browse/HBASE-12285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178471#comment-14178471 ] stack commented on HBASE-12285: --- You have a point [~nkeywal] The idea here is to change log level to see if profuse logging is breaking surefire. Mind if we try the [~dimaspivak] change a while or you thinking we should just go through tests to find the ones that are logging a bunch and do some weeding? Builds are failing, possibly because of SUREFIRE-1091 - Key: HBASE-12285 URL: https://issues.apache.org/jira/browse/HBASE-12285 Project: HBase Issue Type: Bug Affects Versions: 1.0.0 Reporter: Dima Spivak Assignee: Dima Spivak Priority: Blocker Attachments: HBASE-12285_branch-1_v1.patch Our branch-1 builds on builds.apache.org have been failing in recent days after we switched over to an official version of Surefire a few days back (HBASE-4955). The version we're using, 2.17, is hit by a bug ([SUREFIRE-1091|https://jira.codehaus.org/browse/SUREFIRE-1091]) that results in an IOException, which looks like what we're seeing on Jenkins. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12236) Change namespace of HTraceConfiguration dependency in 0.98
[
https://issues.apache.org/jira/browse/HBASE-12236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178472#comment-14178472
]
Ted Yu commented on HBASE-12236:
[~apurtell]:
What do you think ?
Change namespace of HTraceConfiguration dependency in 0.98
--
Key: HBASE-12236
URL: https://issues.apache.org/jira/browse/HBASE-12236
Project: HBase
Issue Type: Bug
Reporter: Ted Yu
Assignee: Ted Yu
Attachments: 12236-v1.txt
As discussed in thread 'NoSuchMethodError using zipkin with hbase 0.98.5',
HBaseSpanReceiver.config() method from htrace-hbase module expects parameter
of type org.htrace.HTraceConfiguration.
However, org.apache.hadoop.hbase.trace.HBaseHTraceConfiguration in 0.98
extends org.cloudera.htrace.HTraceConfiguration , leading to the following
compilation error when building htrace-hbase against 0.98:
{code}
[ERROR]
/home/hadoop/git/htrace/htrace-hbase/src/main/java/org/htrace/impl/HBaseSpanReceiver.java:[341,12]
error: method configure in class HBaseSpanReceiver cannot be applied to
given types;
{code}
Thanks to Abhishek Kumar who reported the above issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-12307) Remove unused Imports
Solomon Duskis created HBASE-12307: -- Summary: Remove unused Imports Key: HBASE-12307 URL: https://issues.apache.org/jira/browse/HBASE-12307 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.2 Reporter: Solomon Duskis Assignee: Solomon Duskis Priority: Minor Remove all of the unused imports. I'll be using eclipse to do that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12308) Fix typo in hbase-rest profile name
Solomon Duskis created HBASE-12308: -- Summary: Fix typo in hbase-rest profile name Key: HBASE-12308 URL: https://issues.apache.org/jira/browse/HBASE-12308 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.2 Reporter: Solomon Duskis Assignee: Solomon Duskis Priority: Minor Change skipRestTets to skipRestTests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Work started] (HBASE-12308) Fix typo in hbase-rest profile name
[ https://issues.apache.org/jira/browse/HBASE-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HBASE-12308 started by Solomon Duskis. -- Fix typo in hbase-rest profile name --- Key: HBASE-12308 URL: https://issues.apache.org/jira/browse/HBASE-12308 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.2 Reporter: Solomon Duskis Assignee: Solomon Duskis Priority: Minor Attachments: HBASE-12308.patch Change skipRestTets to skipRestTests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12308) Fix typo in hbase-rest profile name
[ https://issues.apache.org/jira/browse/HBASE-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solomon Duskis updated HBASE-12308: --- Status: Patch Available (was: In Progress) Fix typo in hbase-rest profile name --- Key: HBASE-12308 URL: https://issues.apache.org/jira/browse/HBASE-12308 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.2 Reporter: Solomon Duskis Assignee: Solomon Duskis Priority: Minor Attachments: HBASE-12308.patch Change skipRestTets to skipRestTests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12308) Fix typo in hbase-rest profile name
[ https://issues.apache.org/jira/browse/HBASE-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solomon Duskis updated HBASE-12308: --- Attachment: HBASE-12308.patch made the one line change. Fix typo in hbase-rest profile name --- Key: HBASE-12308 URL: https://issues.apache.org/jira/browse/HBASE-12308 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.2 Reporter: Solomon Duskis Assignee: Solomon Duskis Priority: Minor Attachments: HBASE-12308.patch Change skipRestTets to skipRestTests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12309) Customize Java Heap min/max settings for individual processes
Mark Tse created HBASE-12309: Summary: Customize Java Heap min/max settings for individual processes Key: HBASE-12309 URL: https://issues.apache.org/jira/browse/HBASE-12309 Project: HBase Issue Type: Improvement Components: master, regionserver, REST Affects Versions: 0.99.1, 0.98.5 Reporter: Mark Tse Priority: Minor The separate processes (master, regionserver, zookeeper, rest, etc.) all run using $JAVA_HEAP_MAX in 'bin/hbase'. However, there may be cases where we want the processes to run with different Java max heap sizes. In 0.98.5, HBASE_(.*)_OPTS variables exist for these processes and can be used to add the Xms and Xmx tags, but because of how the default for JAVA_HEAP_MAX is set, it will always add '-Xmx1000m' to the final call to start up the master/regionserver/rest process, resulting in two different Java heap settings (e.g. -Xmx1000m and -Xmx8g is used when starting the master). In 0.99.1, this default no longer exists so HBASE_(.*)_OPTS is usable, but it would be nice to have dedicated variables for each process. This issue also exists in Hadoop HDFS ([HDFS-7255]). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12281) ClonedPrefixTreeCell should implement HeapSize
[ https://issues.apache.org/jira/browse/HBASE-12281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178539#comment-14178539 ] Hudson commented on HBASE-12281: FAILURE: Integrated in HBase-1.0 #333 (See [https://builds.apache.org/job/HBase-1.0/333/]) HBASE-12281 ClonedPrefixTreeCell should implement HeapSize (Ram) (ramkrishna: rev a4169e7b0408d217e98c34edb2579c1a9bc89ba9) * hbase-prefix-tree/src/main/java/org/apache/hadoop/hbase/codec/prefixtree/PrefixTreeSeeker.java * hbase-common/src/main/java/org/apache/hadoop/hbase/io/encoding/BufferedDataBlockEncoder.java ClonedPrefixTreeCell should implement HeapSize -- Key: HBASE-12281 URL: https://issues.apache.org/jira/browse/HBASE-12281 Project: HBase Issue Type: Bug Affects Versions: 0.99.1 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0, 0.99.2 Attachments: HBASE-12281.patch, HBASE-12281_1.patch, HBASE-12281_2.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (HBASE-12281) ClonedPrefixTreeCell should implement HeapSize
[ https://issues.apache.org/jira/browse/HBASE-12281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan resolved HBASE-12281. Resolution: Fixed Hadoop Flags: Reviewed ClonedPrefixTreeCell should implement HeapSize -- Key: HBASE-12281 URL: https://issues.apache.org/jira/browse/HBASE-12281 Project: HBase Issue Type: Bug Affects Versions: 0.99.1 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0, 0.99.2 Attachments: HBASE-12281.patch, HBASE-12281_1.patch, HBASE-12281_2.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12281) ClonedPrefixTreeCell should implement HeapSize
[ https://issues.apache.org/jira/browse/HBASE-12281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178571#comment-14178571 ] Hudson commented on HBASE-12281: FAILURE: Integrated in HBase-TRUNK #5679 (See [https://builds.apache.org/job/HBase-TRUNK/5679/]) HBASE-12281 ClonedPrefixTreeCell should implement HeapSize (Ram) (ramkrishna: rev 31ccaa519b1740db52420646b891b883bdd3b156) * hbase-common/src/main/java/org/apache/hadoop/hbase/io/encoding/BufferedDataBlockEncoder.java * hbase-prefix-tree/src/main/java/org/apache/hadoop/hbase/codec/prefixtree/PrefixTreeSeeker.java ClonedPrefixTreeCell should implement HeapSize -- Key: HBASE-12281 URL: https://issues.apache.org/jira/browse/HBASE-12281 Project: HBase Issue Type: Bug Affects Versions: 0.99.1 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0, 0.99.2 Attachments: HBASE-12281.patch, HBASE-12281_1.patch, HBASE-12281_2.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12286) [shell] Add server/cluster online load of configuration changes
[ https://issues.apache.org/jira/browse/HBASE-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12286: -- Attachment: 0001-Add-doc-to-the-refguide-change-command-names-to-drop.patch [~manukranthk] This is your patch but with commands renamed dropping the '_rs_' (because it may be the case that the master will carry regions in the future -- it used to) and I've added help to the commands and a little section on dynamic config in the refguide. If good by you I'll commit. [shell] Add server/cluster online load of configuration changes --- Key: HBASE-12286 URL: https://issues.apache.org/jira/browse/HBASE-12286 Project: HBase Issue Type: New Feature Components: shell Reporter: stack Assignee: Manukranth Kolloju Fix For: 0.99.2 Attachments: 0001-Add-doc-to-the-refguide-change-command-names-to-drop.patch, 0001-Adding-shell-methods-for-Admin.updateConfiguration.patch, 0001-HBASE-12286-Adding-HBase-Admin-method-for-updating-c.patch Add new loadConfig and loadConfig ServerName verbs to shell to expose new online loading of config changes. This is last piece of a forward port of 0.89fb dynamic config feature done by [~manukranthk] I'll do this last bit if no one else takes it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12282) Ensure Cells and its implementations work with Buffers also
[ https://issues.apache.org/jira/browse/HBASE-12282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-12282: --- Attachment: HBASE-12224_2.patch This patch is like a POC and has some of the subtasks implemented at a high level. Includes Cell level interface changes, API needed for the trackers and how the CellComparator handles BBs and bytes[]. But this would not be the exact way how things will work but will give us an idea how things will shape up once all the subtasks are done. The patch just deals with HFileReader and the StoreScanner. Just ensures that all test cases in TestStore passes except one which needs a change in the bloom filter. Discussing with Anoop on this and just noting down things as and when wanted to make changes were - We lose the optimization done by Vladimir - HBASE-12090 - BBs may have more index and position management internally. BR may come handy here. - If we want to deal with BBs one issue in case of DBB is that max size of integer is the max size of a DBB that can be allocated. How can that be addressed. Can our HFileBlock be bigger than that? - We may need to do some copy from the BB to a byte[] when we create some fake keys or keys like first on row, last on row etc. - We have to ensure that from the HFileREader onwards arrayOffset() should not be called if the BB is offheap. (Not done) - Memstore and memstore impl should support BB. Already subtask raised for it. Anoop's work would be of help here. Can disucss with him. - Write path also needs to handle these BBs in cases of Bloom filters. Some of the steps followed in the patch could be hacky but if we could find ways to address them then we can move towards the goal of BB in read path slowly. Based on the feed back will work on the sub jira raised- from next week as am on vacation for the rest of the week. Ensure Cells and its implementations work with Buffers also --- Key: HBASE-12282 URL: https://issues.apache.org/jira/browse/HBASE-12282 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Affects Versions: 0.99.1 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0, 0.99.2 Attachments: HBASE-12224_2.patch This issue can be used to brainstorm and then do the necessary changes for the offheap work. All impl of cells deal with byte[] but when we change the Hfileblocks/Readers to work purely with Buffers then the byte[] usage would mean that always the data is copied to the onheap. Cell may need some interface change to implement this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12308) Fix typo in hbase-rest profile name
[ https://issues.apache.org/jira/browse/HBASE-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12308: -- Resolution: Fixed Fix Version/s: 0.99.2 0.98.8 2.0.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to 0.98+. Thank you [~sduskis] Fix typo in hbase-rest profile name --- Key: HBASE-12308 URL: https://issues.apache.org/jira/browse/HBASE-12308 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.2 Reporter: Solomon Duskis Assignee: Solomon Duskis Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.2 Attachments: HBASE-12308.patch Change skipRestTets to skipRestTests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12286) [shell] Add server/cluster online load of configuration changes
[ https://issues.apache.org/jira/browse/HBASE-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178593#comment-14178593 ] Manukranth Kolloju commented on HBASE-12286: Sure. That makes total sense. I could have done that change if you wanted, but sure go ahead with the commit. [shell] Add server/cluster online load of configuration changes --- Key: HBASE-12286 URL: https://issues.apache.org/jira/browse/HBASE-12286 Project: HBase Issue Type: New Feature Components: shell Reporter: stack Assignee: Manukranth Kolloju Fix For: 0.99.2 Attachments: 0001-Add-doc-to-the-refguide-change-command-names-to-drop.patch, 0001-Adding-shell-methods-for-Admin.updateConfiguration.patch, 0001-HBASE-12286-Adding-HBase-Admin-method-for-updating-c.patch Add new loadConfig and loadConfig ServerName verbs to shell to expose new online loading of config changes. This is last piece of a forward port of 0.89fb dynamic config feature done by [~manukranthk] I'll do this last bit if no one else takes it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12286) [shell] Add server/cluster online load of configuration changes
[ https://issues.apache.org/jira/browse/HBASE-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178605#comment-14178605 ] stack commented on HBASE-12286: --- bq. I could have done that change if you wanted Thanks. Was just trying to spare you boring stuff (smile) [shell] Add server/cluster online load of configuration changes --- Key: HBASE-12286 URL: https://issues.apache.org/jira/browse/HBASE-12286 Project: HBase Issue Type: New Feature Components: shell Reporter: stack Assignee: Manukranth Kolloju Fix For: 0.99.2 Attachments: 0001-Add-doc-to-the-refguide-change-command-names-to-drop.patch, 0001-Adding-shell-methods-for-Admin.updateConfiguration.patch, 0001-HBASE-12286-Adding-HBase-Admin-method-for-updating-c.patch Add new loadConfig and loadConfig ServerName verbs to shell to expose new online loading of config changes. This is last piece of a forward port of 0.89fb dynamic config feature done by [~manukranthk] I'll do this last bit if no one else takes it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12286) [shell] Add server/cluster online load of configuration changes
[ https://issues.apache.org/jira/browse/HBASE-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12286: -- Release Note: Adds shell commands: update_config 'servername' update_all_config These call new Admin methods added in HBASE-12147 to change server config. Only a small subset of configs are changeable without restart currently mostly to do with compaction configuration. See the refguide on dynamic configuration for a list. [shell] Add server/cluster online load of configuration changes --- Key: HBASE-12286 URL: https://issues.apache.org/jira/browse/HBASE-12286 Project: HBase Issue Type: New Feature Components: shell Reporter: stack Assignee: Manukranth Kolloju Fix For: 0.99.2 Attachments: 0001-Add-doc-to-the-refguide-change-command-names-to-drop.patch, 0001-Adding-shell-methods-for-Admin.updateConfiguration.patch, 0001-HBASE-12286-Adding-HBase-Admin-method-for-updating-c.patch Add new loadConfig and loadConfig ServerName verbs to shell to expose new online loading of config changes. This is last piece of a forward port of 0.89fb dynamic config feature done by [~manukranthk] I'll do this last bit if no one else takes it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12282) Ensure Cells and its implementations work with Buffers also
[ https://issues.apache.org/jira/browse/HBASE-12282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178619#comment-14178619 ] stack commented on HBASE-12282: --- bq. BBs may have more index and position management internally. BR may come handy here. What you thinking here? bq. Can our HFileBlock be bigger than that? 2G is max? int? Else we need to do aggregate of BBs. Thanks for posting patch. Looking at the Cell changes, my immediate thought is that a BB-backed Cell is just a particular implementation of Cell but I think what we are finding is that we are bumping into limitations of a byte-array only based Cell; it won't work if the Cell references DBBs? Is that what you fellas are seeing? And what about BR? Where does it fall down? What are limitations of BR over a BB. Can we write up a doc? It is hard to keep account of all the issues around off-heaping at this stage. Doc could be an offheap read-path and/or an off-heap write-path? Good work lads. Ensure Cells and its implementations work with Buffers also --- Key: HBASE-12282 URL: https://issues.apache.org/jira/browse/HBASE-12282 Project: HBase Issue Type: Sub-task Components: regionserver, Scanners Affects Versions: 0.99.1 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0, 0.99.2 Attachments: HBASE-12224_2.patch This issue can be used to brainstorm and then do the necessary changes for the offheap work. All impl of cells deal with byte[] but when we change the Hfileblocks/Readers to work purely with Buffers then the byte[] usage would mean that always the data is copied to the onheap. Cell may need some interface change to implement this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12301) user_permission command does not show global permissions
[
https://issues.apache.org/jira/browse/HBASE-12301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178622#comment-14178622
]
Jerry He commented on HBASE-12301:
--
bq. showing only the global permission when user_permission is invoked with no
argument. If you want the table permission you have to specify the regex as was
described in the user_permission help
Sounds good!
user_permission command does not show global permissions
Key: HBASE-12301
URL: https://issues.apache.org/jira/browse/HBASE-12301
Project: HBase
Issue Type: Bug
Components: security, shell
Affects Versions: 0.98.4, 2.0.0
Reporter: Jerry He
Assignee: Matteo Bertozzi
Attachments: HBASE-12301-v0.patch
It seems that since 0,98 or later, the shell command does not show global
permission anymore, even requested by user with the right privilege.
{code}
hbase(main):004:0 user_permission
UserTable,Family,Qualifier:Permission
hbase default,table1,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table1,,: [Permission:
actions=READ,WRITE]
hbase default,table2,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table2,,: [Permission:
actions=READ,WRITE]
{code}
I recall in the older versions, global permissions were shown as permissions
on the hbase:acl table.
Anyway we need a way to show the global permissions as part of
user_permission request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12301) user_permission command does not show global permissions
[
https://issues.apache.org/jira/browse/HBASE-12301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Bertozzi updated HBASE-12301:
Status: Patch Available (was: Open)
user_permission command does not show global permissions
Key: HBASE-12301
URL: https://issues.apache.org/jira/browse/HBASE-12301
Project: HBase
Issue Type: Bug
Components: security, shell
Affects Versions: 0.98.4, 2.0.0
Reporter: Jerry He
Assignee: Matteo Bertozzi
Attachments: HBASE-12301-v0.patch
It seems that since 0,98 or later, the shell command does not show global
permission anymore, even requested by user with the right privilege.
{code}
hbase(main):004:0 user_permission
UserTable,Family,Qualifier:Permission
hbase default,table1,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table1,,: [Permission:
actions=READ,WRITE]
hbase default,table2,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table2,,: [Permission:
actions=READ,WRITE]
{code}
I recall in the older versions, global permissions were shown as permissions
on the hbase:acl table.
Anyway we need a way to show the global permissions as part of
user_permission request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12294) Can't build the docs after the hbase-checkstyle module was added
[
https://issues.apache.org/jira/browse/HBASE-12294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178650#comment-14178650
]
Andrew Purtell commented on HBASE-12294:
bq. -Dtest=test is still broken since the checkstyle module does not set
failIfNoTests to false, and hence every run with -Dtest=... will fail.
Cool, let me add that to the patch on HBASE-12299 also. See over there.
We can debate which patch to commit to fix the checkstyle module issues
(HBASE-12299 or another) but we should and I intend to revert the half measures
that have gone in so far on all branches that have not fixed all build issues.
When we have the complete fix ready we can do the reverts then the new commit
at the same time.
Can't build the docs after the hbase-checkstyle module was added
Key: HBASE-12294
URL: https://issues.apache.org/jira/browse/HBASE-12294
Project: HBase
Issue Type: Bug
Components: build
Reporter: Misty Stanley-Jones
Assignee: Elliott Clark
Priority: Blocker
Fix For: 2.0.0, 0.98.8, 0.99.2
Attachments: 0001-HBASE-12294-Fix-site-generation.patch,
HBASE-12294.patch
Since the 15th, I have not been able to build the docs. I get these errors:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on project
hbase-checkstyle: Missing distribution management in project HBase -
Checkstyle (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT) - [Help 1]
{code}
{code}
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on
project hbase-checkstyle: Missing distribution management in project HBase -
Checkstyle (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Missing
distribution management in project HBase - Checkstyle
(org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT)
at
org.apache.maven.plugins.site.AbstractDeployMojo.getSite(AbstractDeployMojo.java:762)
at
org.apache.maven.plugins.site.AbstractDeployMojo.getDeployModuleDirectory(AbstractDeployMojo.java:249)
at
org.apache.maven.plugins.site.AbstractDeployMojo.deploy(AbstractDeployMojo.java:320)
at
org.apache.maven.plugins.site.AbstractDeployMojo.deployTo(AbstractDeployMojo.java:281)
at
org.apache.maven.plugins.site.AbstractDeployMojo.execute(AbstractDeployMojo.java:163)
at org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:75)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
{code}
I'm able to resolve it by adding the attached patch to the POM. [~eclark], is
there a specific reason you didn't use inheritance in the checkstyles module?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12308) Fix typo in hbase-rest profile name
[
https://issues.apache.org/jira/browse/HBASE-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178660#comment-14178660
]
Hadoop QA commented on HBASE-12308:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12676101/HBASE-12308.patch
against trunk revision .
ATTACHMENT ID: 12676101
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{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 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/11416//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11416//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11416//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11416//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11416//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11416//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11416//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11416//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11416//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11416//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11416//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11416//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11416//console
This message is automatically generated.
Fix typo in hbase-rest profile name
---
Key: HBASE-12308
URL: https://issues.apache.org/jira/browse/HBASE-12308
Project: HBase
Issue Type: Bug
Affects Versions: 2.0.0, 0.99.2
Reporter: Solomon Duskis
Assignee: Solomon Duskis
Priority: Minor
Fix For: 2.0.0, 0.98.8, 0.99.2
Attachments: HBASE-12308.patch
Change skipRestTets to skipRestTests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12299) Can't assemble tarballs after HBASE-12261
[
https://issues.apache.org/jira/browse/HBASE-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178662#comment-14178662
]
Sean Busbey commented on HBASE-12299:
-
As a part of this, can we correct the need of the javadoc plugin for
hbase-annotations? Since the root pom specifies the javadoc dependency for all
modules ATM it creates a circular need with the hbase-annotations module.
Can't assemble tarballs after HBASE-12261
-
Key: HBASE-12299
URL: https://issues.apache.org/jira/browse/HBASE-12299
Project: HBase
Issue Type: Bug
Reporter: Andrew Purtell
Priority: Blocker
Attachments: HBASE-12299-0.98.patch, HBASE-12299-branch-1.patch,
HBASE-12299-master.patch, HBASE-12299.patch
{{$ mvn -DskipTests clean install package assembly:single}}
...
ERROR Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Failed to create assembly: Artifact:
org.apache.hbase:hbase-checkstyle:jar:0.98.7 (included by module) does not
have an artifact with a file. Please ensure the package phase is run before
the assembly is generated.
$ {{mvn -DskipTests clean install package mvn -DskipTests assembly:single}}
...
ERROR Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Failed to create assembly: Artifact:
org.apache.hbase:hbase-annotations:jar:0.98.8-SNAPSHOT (included by module)
does not have an artifact with a file. Please ensure the package phase is run
before the assembly is generated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12294) Can't build the docs after the hbase-checkstyle module was added
[
https://issues.apache.org/jira/browse/HBASE-12294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178663#comment-14178663
]
Elliott Clark commented on HBASE-12294:
---
When I add the parent to hbase-checkstyle I am able to {code} mvn clean test
-Dtest=TestFromClientSide{code}
Can't build the docs after the hbase-checkstyle module was added
Key: HBASE-12294
URL: https://issues.apache.org/jira/browse/HBASE-12294
Project: HBase
Issue Type: Bug
Components: build
Reporter: Misty Stanley-Jones
Assignee: Elliott Clark
Priority: Blocker
Fix For: 2.0.0, 0.98.8, 0.99.2
Attachments: 0001-HBASE-12294-Fix-site-generation.patch,
HBASE-12294.patch
Since the 15th, I have not been able to build the docs. I get these errors:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on project
hbase-checkstyle: Missing distribution management in project HBase -
Checkstyle (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT) - [Help 1]
{code}
{code}
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on
project hbase-checkstyle: Missing distribution management in project HBase -
Checkstyle (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Missing
distribution management in project HBase - Checkstyle
(org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT)
at
org.apache.maven.plugins.site.AbstractDeployMojo.getSite(AbstractDeployMojo.java:762)
at
org.apache.maven.plugins.site.AbstractDeployMojo.getDeployModuleDirectory(AbstractDeployMojo.java:249)
at
org.apache.maven.plugins.site.AbstractDeployMojo.deploy(AbstractDeployMojo.java:320)
at
org.apache.maven.plugins.site.AbstractDeployMojo.deployTo(AbstractDeployMojo.java:281)
at
org.apache.maven.plugins.site.AbstractDeployMojo.execute(AbstractDeployMojo.java:163)
at org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:75)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
{code}
I'm able to resolve it by adding the attached patch to the POM. [~eclark], is
there a specific reason you didn't use inheritance in the checkstyles module?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12307) Remove unused Imports in hbase-client and hbase-common
[ https://issues.apache.org/jira/browse/HBASE-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solomon Duskis updated HBASE-12307: --- Summary: Remove unused Imports in hbase-client and hbase-common (was: Remove unused Imports) Remove unused Imports in hbase-client and hbase-common -- Key: HBASE-12307 URL: https://issues.apache.org/jira/browse/HBASE-12307 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.2 Reporter: Solomon Duskis Assignee: Solomon Duskis Priority: Minor Attachments: HBASE-12307.patch Remove all of the unused imports. I'll be using eclipse to do that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12307) Remove unused Imports
[ https://issues.apache.org/jira/browse/HBASE-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solomon Duskis updated HBASE-12307: --- Attachment: HBASE-12307.patch Started with hbase-client and hbase-common. Remove unused Imports - Key: HBASE-12307 URL: https://issues.apache.org/jira/browse/HBASE-12307 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.2 Reporter: Solomon Duskis Assignee: Solomon Duskis Priority: Minor Attachments: HBASE-12307.patch Remove all of the unused imports. I'll be using eclipse to do that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12299) Can't assemble tarballs after HBASE-12261
[
https://issues.apache.org/jira/browse/HBASE-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178672#comment-14178672
]
Andrew Purtell commented on HBASE-12299:
bq. As a part of this, can we correct the need of the javadoc plugin for
hbase-annotations?
I think that should be a separate issue.
We are having a problem right now staging 0.98.7 to our internal Nexus because
the system scope dependency on tools.jar is disallowed by the default Nexus
rule set. System scope dependencies will apparently not be supported in Maven
4. I'd like to question the need for a custom Javadoc processor entirely in a
different issue. Maybe we can rip that all out.
Can't assemble tarballs after HBASE-12261
-
Key: HBASE-12299
URL: https://issues.apache.org/jira/browse/HBASE-12299
Project: HBase
Issue Type: Bug
Reporter: Andrew Purtell
Priority: Blocker
Attachments: HBASE-12299-0.98.patch, HBASE-12299-branch-1.patch,
HBASE-12299-master.patch, HBASE-12299.patch
{{$ mvn -DskipTests clean install package assembly:single}}
...
ERROR Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Failed to create assembly: Artifact:
org.apache.hbase:hbase-checkstyle:jar:0.98.7 (included by module) does not
have an artifact with a file. Please ensure the package phase is run before
the assembly is generated.
$ {{mvn -DskipTests clean install package mvn -DskipTests assembly:single}}
...
ERROR Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Failed to create assembly: Artifact:
org.apache.hbase:hbase-annotations:jar:0.98.8-SNAPSHOT (included by module)
does not have an artifact with a file. Please ensure the package phase is run
before the assembly is generated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12307) Remove unused Imports
[ https://issues.apache.org/jira/browse/HBASE-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Solomon Duskis updated HBASE-12307: --- Status: Patch Available (was: Open) Remove unused Imports - Key: HBASE-12307 URL: https://issues.apache.org/jira/browse/HBASE-12307 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.2 Reporter: Solomon Duskis Assignee: Solomon Duskis Priority: Minor Attachments: HBASE-12307.patch Remove all of the unused imports. I'll be using eclipse to do that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12307) Remove unused Imports in hbase-client and hbase-common
[ https://issues.apache.org/jira/browse/HBASE-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178674#comment-14178674 ] Solomon Duskis commented on HBASE-12307: I ran eclipse's optimize imports. Some unused imports were removed, and most files had some form of import reorganization. Remove unused Imports in hbase-client and hbase-common -- Key: HBASE-12307 URL: https://issues.apache.org/jira/browse/HBASE-12307 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.2 Reporter: Solomon Duskis Assignee: Solomon Duskis Priority: Minor Attachments: HBASE-12307.patch Remove all of the unused imports. I'll be using eclipse to do that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12299) Can't assemble tarballs after HBASE-12261
[
https://issues.apache.org/jira/browse/HBASE-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178675#comment-14178675
]
Andrew Purtell commented on HBASE-12299:
bq. -Dtest=test is still broken since the checkstyle module does not set
failIfNoTests to false, and hence every run with -Dtest=... will fail.
I'm going to put up a new patch set including a fix for this momentarily.
Dealing with an internal issue at the moment (see above comment).
Can't assemble tarballs after HBASE-12261
-
Key: HBASE-12299
URL: https://issues.apache.org/jira/browse/HBASE-12299
Project: HBase
Issue Type: Bug
Reporter: Andrew Purtell
Priority: Blocker
Attachments: HBASE-12299-0.98.patch, HBASE-12299-branch-1.patch,
HBASE-12299-master.patch, HBASE-12299.patch
{{$ mvn -DskipTests clean install package assembly:single}}
...
ERROR Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Failed to create assembly: Artifact:
org.apache.hbase:hbase-checkstyle:jar:0.98.7 (included by module) does not
have an artifact with a file. Please ensure the package phase is run before
the assembly is generated.
$ {{mvn -DskipTests clean install package mvn -DskipTests assembly:single}}
...
ERROR Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Failed to create assembly: Artifact:
org.apache.hbase:hbase-annotations:jar:0.98.8-SNAPSHOT (included by module)
does not have an artifact with a file. Please ensure the package phase is run
before the assembly is generated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12299) Can't assemble tarballs after HBASE-12261
[
https://issues.apache.org/jira/browse/HBASE-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178682#comment-14178682
]
Andrew Purtell commented on HBASE-12299:
Also let me check if that's actually needed. [~lhofhansl] might have been using
what's checked in not one of the patches that adds the parent.
Can't assemble tarballs after HBASE-12261
-
Key: HBASE-12299
URL: https://issues.apache.org/jira/browse/HBASE-12299
Project: HBase
Issue Type: Bug
Reporter: Andrew Purtell
Priority: Blocker
Attachments: HBASE-12299-0.98.patch, HBASE-12299-branch-1.patch,
HBASE-12299-master.patch, HBASE-12299.patch
{{$ mvn -DskipTests clean install package assembly:single}}
...
ERROR Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Failed to create assembly: Artifact:
org.apache.hbase:hbase-checkstyle:jar:0.98.7 (included by module) does not
have an artifact with a file. Please ensure the package phase is run before
the assembly is generated.
$ {{mvn -DskipTests clean install package mvn -DskipTests assembly:single}}
...
ERROR Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Failed to create assembly: Artifact:
org.apache.hbase:hbase-annotations:jar:0.98.8-SNAPSHOT (included by module)
does not have an artifact with a file. Please ensure the package phase is run
before the assembly is generated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12307) Remove unused Imports in hbase-client and hbase-common
[
https://issues.apache.org/jira/browse/HBASE-12307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178695#comment-14178695
]
Hadoop QA commented on HBASE-12307:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12676124/HBASE-12307.patch
against trunk revision .
ATTACHMENT ID: 12676124
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 102
new or modified tests.
{color:red}-1 javac{color}. The patch appears to cause mvn compile goal to
fail.
Compilation errors resume:
[ERROR] COMPILATION ERROR :
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-common/src/main/java/org/apache/hadoop/hbase/util/Bytes.java:[1433,3]
error: cannot find symbol
[ERROR] symbol: class VisibleForTesting
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-common/src/main/java/org/apache/hadoop/hbase/util/Bytes.java:[1487,19]
Unsafe is internal proprietary API and may be removed in a future release
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-common/src/main/java/org/apache/hadoop/hbase/util/Bytes.java:[1493,21]
Unsafe is internal proprietary API and may be removed in a future release
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-common/src/main/java/org/apache/hadoop/hbase/util/Bytes.java:[1498,28]
Unsafe is internal proprietary API and may be removed in a future release
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile)
on project hbase-common: Compilation failure: Compilation failure:
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-common/src/main/java/org/apache/hadoop/hbase/util/Bytes.java:[1433,3]
error: cannot find symbol
[ERROR] symbol: class VisibleForTesting
[ERROR] location: class Bytes
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-common/src/main/java/org/apache/hadoop/hbase/util/Bytes.java:[53,15]
Unsafe is internal proprietary API and may be removed in a future release
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-common/src/main/java/org/apache/hadoop/hbase/util/Bytes.java:[1487,19]
Unsafe is internal proprietary API and may be removed in a future release
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-common/src/main/java/org/apache/hadoop/hbase/util/Bytes.java:[1493,21]
Unsafe is internal proprietary API and may be removed in a future release
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase-common/src/main/java/org/apache/hadoop/hbase/util/Bytes.java:[1498,28]
Unsafe is internal proprietary API and may be removed in a future release
[ERROR] - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn goals -rf :hbase-common
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11419//console
This message is automatically generated.
Remove unused Imports in hbase-client and hbase-common
--
Key: HBASE-12307
URL: https://issues.apache.org/jira/browse/HBASE-12307
Project: HBase
Issue Type: Bug
Affects Versions: 2.0.0, 0.99.2
Reporter: Solomon Duskis
Assignee: Solomon Duskis
Priority: Minor
Attachments: HBASE-12307.patch
Remove all of the unused imports. I'll be using eclipse to do that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-12294) Can't build the docs after the hbase-checkstyle module was added
[
https://issues.apache.org/jira/browse/HBASE-12294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliott Clark updated HBASE-12294:
--
Attachment: 0001-HBASE-12294-Addendum.patch
Can't build the docs after the hbase-checkstyle module was added
Key: HBASE-12294
URL: https://issues.apache.org/jira/browse/HBASE-12294
Project: HBase
Issue Type: Bug
Components: build
Reporter: Misty Stanley-Jones
Assignee: Elliott Clark
Priority: Blocker
Fix For: 2.0.0, 0.98.8, 0.99.2
Attachments: 0001-HBASE-12294-Addendum.patch,
0001-HBASE-12294-Fix-site-generation.patch, HBASE-12294.patch
Since the 15th, I have not been able to build the docs. I get these errors:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on project
hbase-checkstyle: Missing distribution management in project HBase -
Checkstyle (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT) - [Help 1]
{code}
{code}
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on
project hbase-checkstyle: Missing distribution management in project HBase -
Checkstyle (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Missing
distribution management in project HBase - Checkstyle
(org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT)
at
org.apache.maven.plugins.site.AbstractDeployMojo.getSite(AbstractDeployMojo.java:762)
at
org.apache.maven.plugins.site.AbstractDeployMojo.getDeployModuleDirectory(AbstractDeployMojo.java:249)
at
org.apache.maven.plugins.site.AbstractDeployMojo.deploy(AbstractDeployMojo.java:320)
at
org.apache.maven.plugins.site.AbstractDeployMojo.deployTo(AbstractDeployMojo.java:281)
at
org.apache.maven.plugins.site.AbstractDeployMojo.execute(AbstractDeployMojo.java:163)
at org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:75)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
{code}
I'm able to resolve it by adding the attached patch to the POM. [~eclark], is
there a specific reason you didn't use inheritance in the checkstyles module?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12299) Can't assemble tarballs after HBASE-12261
[
https://issues.apache.org/jira/browse/HBASE-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178707#comment-14178707
]
Andrew Purtell commented on HBASE-12299:
I filed HBASE-12310 for the hbase-annotations javadoc issues
Can't assemble tarballs after HBASE-12261
-
Key: HBASE-12299
URL: https://issues.apache.org/jira/browse/HBASE-12299
Project: HBase
Issue Type: Bug
Reporter: Andrew Purtell
Priority: Blocker
Attachments: HBASE-12299-0.98.patch, HBASE-12299-branch-1.patch,
HBASE-12299-master.patch, HBASE-12299.patch
{{$ mvn -DskipTests clean install package assembly:single}}
...
ERROR Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Failed to create assembly: Artifact:
org.apache.hbase:hbase-checkstyle:jar:0.98.7 (included by module) does not
have an artifact with a file. Please ensure the package phase is run before
the assembly is generated.
$ {{mvn -DskipTests clean install package mvn -DskipTests assembly:single}}
...
ERROR Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Failed to create assembly: Artifact:
org.apache.hbase:hbase-annotations:jar:0.98.8-SNAPSHOT (included by module)
does not have an artifact with a file. Please ensure the package phase is run
before the assembly is generated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-12310) Remove custom doclet from hbase-annotations
Andrew Purtell created HBASE-12310: -- Summary: Remove custom doclet from hbase-annotations Key: HBASE-12310 URL: https://issues.apache.org/jira/browse/HBASE-12310 Project: HBase Issue Type: Bug Reporter: Andrew Purtell hbase-annotations includes a custom doclet used for filtering APIs out of the user API javadoc given our project specific interface annotations. However, this is problematic for a few reasons: - To build the doclet we include a system scope dependency to tools.jar. Default Nexus rules disallow that. Staging downstream HBase artifacts will be problematic. I don't know how we were able to release 0.98.7 with this in place. I think someone will be looking into the Apache Nexus configuration. - As I understand it, system scope dependencies will not be supported by Maven 4 because they've been determined to be generally problematic. - As [~busbey] mentioned on HBASE-12299, the root pom specifies the javadoc dependency for all modules and it creates a circular need with the hbase-annotations module. Do we really need a custom doclet? Can we simply remove all of this? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12308) Fix typo in hbase-rest profile name
[ https://issues.apache.org/jira/browse/HBASE-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178713#comment-14178713 ] Hudson commented on HBASE-12308: FAILURE: Integrated in HBase-1.0 #334 (See [https://builds.apache.org/job/HBase-1.0/334/]) HBASE-12308 Fix typo in hbase-rest profile name (Solomon Duskis) (stack: rev 43a04baebe58df1334d9594dac72ce268d228c02) * hbase-rest/pom.xml Fix typo in hbase-rest profile name --- Key: HBASE-12308 URL: https://issues.apache.org/jira/browse/HBASE-12308 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.2 Reporter: Solomon Duskis Assignee: Solomon Duskis Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.2 Attachments: HBASE-12308.patch Change skipRestTets to skipRestTests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12294) Can't build the docs after the hbase-checkstyle module was added
[
https://issues.apache.org/jira/browse/HBASE-12294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178721#comment-14178721
]
Andrew Purtell commented on HBASE-12294:
[~eclark] what do you think about tucking hbase-checkstyle under a common
directory for build time infrastructure? See HBASE-12299. No problem if you'd
like to take that over if you think it's a reasonable idea. Otherwise I think
we are going to end up with a few build infrastructure modules littering the
top level and both I and [~busbey] above have suggested we might want to avoid
that.
Can't build the docs after the hbase-checkstyle module was added
Key: HBASE-12294
URL: https://issues.apache.org/jira/browse/HBASE-12294
Project: HBase
Issue Type: Bug
Components: build
Reporter: Misty Stanley-Jones
Assignee: Elliott Clark
Priority: Blocker
Fix For: 2.0.0, 0.98.8, 0.99.2
Attachments: 0001-HBASE-12294-Addendum.patch,
0001-HBASE-12294-Fix-site-generation.patch, HBASE-12294.patch
Since the 15th, I have not been able to build the docs. I get these errors:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on project
hbase-checkstyle: Missing distribution management in project HBase -
Checkstyle (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT) - [Help 1]
{code}
{code}
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on
project hbase-checkstyle: Missing distribution management in project HBase -
Checkstyle (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Missing
distribution management in project HBase - Checkstyle
(org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT)
at
org.apache.maven.plugins.site.AbstractDeployMojo.getSite(AbstractDeployMojo.java:762)
at
org.apache.maven.plugins.site.AbstractDeployMojo.getDeployModuleDirectory(AbstractDeployMojo.java:249)
at
org.apache.maven.plugins.site.AbstractDeployMojo.deploy(AbstractDeployMojo.java:320)
at
org.apache.maven.plugins.site.AbstractDeployMojo.deployTo(AbstractDeployMojo.java:281)
at
org.apache.maven.plugins.site.AbstractDeployMojo.execute(AbstractDeployMojo.java:163)
at org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:75)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
{code}
I'm able to resolve it by adding the attached patch to the POM. [~eclark], is
there a specific reason you didn't use inheritance in the checkstyles module?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12310) Remove custom doclet from hbase-annotations
[ https://issues.apache.org/jira/browse/HBASE-12310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178731#comment-14178731 ] Andrew Purtell commented on HBASE-12310: Understood that we needed to clone/fork the Hadoop doclet code once we created our own interface annotations. Maybe we do not and should not need to use Hadoop's custom doclet either. Remove custom doclet from hbase-annotations --- Key: HBASE-12310 URL: https://issues.apache.org/jira/browse/HBASE-12310 Project: HBase Issue Type: Bug Reporter: Andrew Purtell hbase-annotations includes a custom doclet used for filtering APIs out of the user API javadoc given our project specific interface annotations. However, this is problematic for a few reasons: - To build the doclet we include a system scope dependency to tools.jar. Default Nexus rules disallow that. Staging downstream HBase artifacts will be problematic. I don't know how we were able to release 0.98.7 with this in place. I think someone will be looking into the Apache Nexus configuration. - As I understand it, system scope dependencies will not be supported by Maven 4 because they've been determined to be generally problematic. - As [~busbey] mentioned on HBASE-12299, the root pom specifies the javadoc dependency for all modules and it creates a circular need with the hbase-annotations module. Do we really need a custom doclet? Can we simply remove all of this? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (HBASE-12310) Remove custom doclet from hbase-annotations
[ https://issues.apache.org/jira/browse/HBASE-12310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178731#comment-14178731 ] Andrew Purtell edited comment on HBASE-12310 at 10/21/14 5:54 PM: -- Understood that we needed to clone/fork the Hadoop doclet code once we created our own interface annotations. Maybe we do not and should not need to use Hadoop's custom doclet either. If they are using the same build time configuration to build their doclet I'm not sure what the long term disposition of it is. Maybe there is some way to filter what we want with the default doclet. Maybe creating user API docs is problematic enough to not be worth the hassle. For discussion. was (Author: apurtell): Understood that we needed to clone/fork the Hadoop doclet code once we created our own interface annotations. Maybe we do not and should not need to use Hadoop's custom doclet either. Remove custom doclet from hbase-annotations --- Key: HBASE-12310 URL: https://issues.apache.org/jira/browse/HBASE-12310 Project: HBase Issue Type: Bug Reporter: Andrew Purtell hbase-annotations includes a custom doclet used for filtering APIs out of the user API javadoc given our project specific interface annotations. However, this is problematic for a few reasons: - To build the doclet we include a system scope dependency to tools.jar. Default Nexus rules disallow that. Staging downstream HBase artifacts will be problematic. I don't know how we were able to release 0.98.7 with this in place. I think someone will be looking into the Apache Nexus configuration. - As I understand it, system scope dependencies will not be supported by Maven 4 because they've been determined to be generally problematic. - As [~busbey] mentioned on HBASE-12299, the root pom specifies the javadoc dependency for all modules and it creates a circular need with the hbase-annotations module. Do we really need a custom doclet? Can we simply remove all of this? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-12311) Version stats in HFiles?
Lars Hofhansl created HBASE-12311: - Summary: Version stats in HFiles? Key: HBASE-12311 URL: https://issues.apache.org/jira/browse/HBASE-12311 Project: HBase Issue Type: Brainstorming Reporter: Lars Hofhansl In HBASE-9778 I basically punted the decision on whether doing repeated scanner.next() called instead of the issueing (re)seeks to the user. I think we can do better. One way do that is maintain simple stats of what the maximum number of versions we've seen for any row/col combination and store these in the HFile's metadata (just like the timerange, oldest Put, etc). Then we estimate fairly accurately whether we have to expect lots of versions (i.e. seek between columns is better) or not (in which case we'd issue repeated next()'s). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12286) [shell] Add server/cluster online load of configuration changes
[
https://issues.apache.org/jira/browse/HBASE-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178744#comment-14178744
]
Hadoop QA commented on HBASE-12286:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12676113/0001-Add-doc-to-the-refguide-change-command-names-to-drop.patch
against trunk revision .
ATTACHMENT ID: 12676113
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{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:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ raise(ArgumentError, BloomFilter type #{bloomtype} is not
supported. Use one of +
org.apache.hadoop.hbase.regionserver.StoreFile::BloomType.constants.join( ))
+ link
xlink:href=https://issues.apache.org/jira/browse/HBASE-12147;HBASE-12147
Porting Online Config Change from 89-fb/link.
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/11417//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11417//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11417//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11417//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11417//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11417//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11417//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11417//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11417//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11417//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11417//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11417//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11417//console
This message is automatically generated.
[shell] Add server/cluster online load of configuration changes
---
Key: HBASE-12286
URL: https://issues.apache.org/jira/browse/HBASE-12286
Project: HBase
Issue Type: New Feature
Components: shell
Reporter: stack
Assignee: Manukranth Kolloju
Fix For: 0.99.2
Attachments:
0001-Add-doc-to-the-refguide-change-command-names-to-drop.patch,
0001-Adding-shell-methods-for-Admin.updateConfiguration.patch,
0001-HBASE-12286-Adding-HBase-Admin-method-for-updating-c.patch
Add new loadConfig and loadConfig ServerName verbs to shell to expose new
online loading of config changes.
This is last piece of a forward port of 0.89fb dynamic config feature done by
[~manukranthk]
I'll do this last bit if no one else takes it up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12311) Version stats in HFiles?
[ https://issues.apache.org/jira/browse/HBASE-12311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178748#comment-14178748 ] Lars Hofhansl commented on HBASE-12311: --- Are there better/other ideas? The core issue we want to get to: If a (re)seek would get us to a different HFile block we should seek, otherwise repeated next()'s inside the block is (far) more efficient. This decision would need to be made efficient - without needing a bunch of compares of the row-key. Tracking the maximum number of versions seen would a possible and relatively cheap proxy to guess the likelihood of a seek getting us out of the current block. Version stats in HFiles? Key: HBASE-12311 URL: https://issues.apache.org/jira/browse/HBASE-12311 Project: HBase Issue Type: Brainstorming Reporter: Lars Hofhansl In HBASE-9778 I basically punted the decision on whether doing repeated scanner.next() called instead of the issueing (re)seeks to the user. I think we can do better. One way do that is maintain simple stats of what the maximum number of versions we've seen for any row/col combination and store these in the HFile's metadata (just like the timerange, oldest Put, etc). Then we estimate fairly accurately whether we have to expect lots of versions (i.e. seek between columns is better) or not (in which case we'd issue repeated next()'s). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12299) Can't assemble tarballs after HBASE-12261
[
https://issues.apache.org/jira/browse/HBASE-12299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178752#comment-14178752
]
Andrew Purtell commented on HBASE-12299:
We don't need any additional changes to get {{-Dtest=...}} working after the
checkstyle module has been hooked up to the parent. Just checked with the patch
on this issue.
{noformat}
$ mvn clean install -Dtest=TestAtomicOperation -DskipITs
...
---
T E S T S
---
Running org.apache.hadoop.hbase.regionserver.TestAtomicOperation
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 34.092 sec
Results :
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
...
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 01:29 min
[INFO] Finished at: 2014-10-21T11:02:31-08:00
[INFO] Final Memory: 122M/1171M
{noformat}
Can't assemble tarballs after HBASE-12261
-
Key: HBASE-12299
URL: https://issues.apache.org/jira/browse/HBASE-12299
Project: HBase
Issue Type: Bug
Reporter: Andrew Purtell
Priority: Blocker
Attachments: HBASE-12299-0.98.patch, HBASE-12299-branch-1.patch,
HBASE-12299-master.patch, HBASE-12299.patch
{{$ mvn -DskipTests clean install package assembly:single}}
...
ERROR Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Failed to create assembly: Artifact:
org.apache.hbase:hbase-checkstyle:jar:0.98.7 (included by module) does not
have an artifact with a file. Please ensure the package phase is run before
the assembly is generated.
$ {{mvn -DskipTests clean install package mvn -DskipTests assembly:single}}
...
ERROR Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.4:single (default-cli) on
project hbase-assembly: Failed to create assembly: Artifact:
org.apache.hbase:hbase-annotations:jar:0.98.8-SNAPSHOT (included by module)
does not have an artifact with a file. Please ensure the package phase is run
before the assembly is generated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12303) Seek to next row after family delete markers
[ https://issues.apache.org/jira/browse/HBASE-12303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178765#comment-14178765 ] Lars Hofhansl commented on HBASE-12303: --- Opened HBASE-12311 for more brainstorming around this. Seek to next row after family delete markers Key: HBASE-12303 URL: https://issues.apache.org/jira/browse/HBASE-12303 Project: HBase Issue Type: Bug Reporter: Lars Hofhansl Attachments: 12303.txt Currently we seek to the next column when we encounter a family delete marker. I think we safely seek the current store to next row. We ran into a scenario with very slow scans after a lot of rows have been deleted with family delete markers. Some profiling revealed that we seek for once for each row and column. This won't make this go away entirely, but at least we can seek once per row rather than once per column. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12277) Refactor bulkLoad methods in AccessController to its own interface
[ https://issues.apache.org/jira/browse/HBASE-12277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178767#comment-14178767 ] Devaraj Das commented on HBASE-12277: - +1 Refactor bulkLoad methods in AccessController to its own interface -- Key: HBASE-12277 URL: https://issues.apache.org/jira/browse/HBASE-12277 Project: HBase Issue Type: Bug Reporter: Madhan Neethiraj Attachments: 0001-HBASE-12277-Refactored-bulk-load-methods-from-Access.patch, 0002-HBASE-12277-License-text-added-to-the-newly-created-.patch, HBASE-12277-v2.patch, HBASE-12277.patch SecureBulkLoadEndPoint references couple of methods, prePrepareBulkLoad() and preCleanupBulkLoad(), implemented in AccessController i.e. direct coupling between AccessController and SecureBuikLoadEndPoint classes. SecureBulkLoadEndPoint assumes presence of AccessController in secure-cluster. If HBase is configured with another coprocessor for access-control, SecureBulkLoadEndPoint fails with NPE. To remove this direct coupling, bulk-load related methods in AccessController should be refactored to an interface; and have AccessController implement this interfaces. SecureBulkLoadEndPoint should then look for coprocessors that implement this interface, instead of directly looking for AccessController. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12302) VisibilityClient getAuths does not propagate remote service exception correctly
[
https://issues.apache.org/jira/browse/HBASE-12302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerry He updated HBASE-12302:
-
Attachment: HBASE-12302-master-v2.patch
VisibilityClient getAuths does not propagate remote service exception
correctly
---
Key: HBASE-12302
URL: https://issues.apache.org/jira/browse/HBASE-12302
Project: HBase
Issue Type: Bug
Components: Client, security
Affects Versions: 2.0.0, 0.98.7
Reporter: Jerry He
Assignee: Jerry He
Priority: Minor
Fix For: 2.0.0, 0.98.8, 0.99.2
Attachments: HBASE-12302-master-v2.patch, HBASE-12302-master.patch
From hbase shell, run 'get_auths' with a non-superuser:
{code}
hbase(main):002:0 get_auths 'user2'
ERROR:
Here is some help for this command:
Get the visibility labels set for a particular user
Syntax : get_auths 'user1'
For example:
hbase get_auths 'user1'
{code}
We should expect a AccessDeniedException from the server.
From a Java client, AccessDeniedException was dumped out, but the end
exception is
{code}
java.util.NoSuchElementException
at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1124)
at java.util.TreeMap$ValueIterator.next(TreeMap.java:1171)
at
org.apache.hadoop.hbase.security.visibility.VisibilityClient.getAuths(VisibilityClient.java:148)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12308) Fix typo in hbase-rest profile name
[ https://issues.apache.org/jira/browse/HBASE-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178772#comment-14178772 ] Hudson commented on HBASE-12308: FAILURE: Integrated in HBase-TRUNK #5680 (See [https://builds.apache.org/job/HBase-TRUNK/5680/]) HBASE-12308 Fix typo in hbase-rest profile name (Solomon Duskis) (stack: rev 775326907f70123264ceed4246645bc9504d46e4) * hbase-rest/pom.xml Fix typo in hbase-rest profile name --- Key: HBASE-12308 URL: https://issues.apache.org/jira/browse/HBASE-12308 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.2 Reporter: Solomon Duskis Assignee: Solomon Duskis Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.2 Attachments: HBASE-12308.patch Change skipRestTets to skipRestTests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12302) VisibilityClient getAuths does not propagate remote service exception correctly
[
https://issues.apache.org/jira/browse/HBASE-12302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178778#comment-14178778
]
Jerry He commented on HBASE-12302:
--
Attached v2 that addressed Anoop's comment. Also fixed a nit.
VisibilityClient getAuths does not propagate remote service exception
correctly
---
Key: HBASE-12302
URL: https://issues.apache.org/jira/browse/HBASE-12302
Project: HBase
Issue Type: Bug
Components: Client, security
Affects Versions: 2.0.0, 0.98.7
Reporter: Jerry He
Assignee: Jerry He
Priority: Minor
Fix For: 2.0.0, 0.98.8, 0.99.2
Attachments: HBASE-12302-master-v2.patch, HBASE-12302-master.patch
From hbase shell, run 'get_auths' with a non-superuser:
{code}
hbase(main):002:0 get_auths 'user2'
ERROR:
Here is some help for this command:
Get the visibility labels set for a particular user
Syntax : get_auths 'user1'
For example:
hbase get_auths 'user1'
{code}
We should expect a AccessDeniedException from the server.
From a Java client, AccessDeniedException was dumped out, but the end
exception is
{code}
java.util.NoSuchElementException
at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1124)
at java.util.TreeMap$ValueIterator.next(TreeMap.java:1171)
at
org.apache.hadoop.hbase.security.visibility.VisibilityClient.getAuths(VisibilityClient.java:148)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12302) VisibilityClient getAuths does not propagate remote service exception correctly
[
https://issues.apache.org/jira/browse/HBASE-12302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178781#comment-14178781
]
Ted Yu commented on HBASE-12302:
lgtm
Waiting for QA run.
VisibilityClient getAuths does not propagate remote service exception
correctly
---
Key: HBASE-12302
URL: https://issues.apache.org/jira/browse/HBASE-12302
Project: HBase
Issue Type: Bug
Components: Client, security
Affects Versions: 2.0.0, 0.98.7
Reporter: Jerry He
Assignee: Jerry He
Priority: Minor
Fix For: 2.0.0, 0.98.8, 0.99.2
Attachments: HBASE-12302-master-v2.patch, HBASE-12302-master.patch
From hbase shell, run 'get_auths' with a non-superuser:
{code}
hbase(main):002:0 get_auths 'user2'
ERROR:
Here is some help for this command:
Get the visibility labels set for a particular user
Syntax : get_auths 'user1'
For example:
hbase get_auths 'user1'
{code}
We should expect a AccessDeniedException from the server.
From a Java client, AccessDeniedException was dumped out, but the end
exception is
{code}
java.util.NoSuchElementException
at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1124)
at java.util.TreeMap$ValueIterator.next(TreeMap.java:1171)
at
org.apache.hadoop.hbase.security.visibility.VisibilityClient.getAuths(VisibilityClient.java:148)
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11419) After increasing TTL value of a hbase table having pre-split regions and decreasing TTL value, table becomes inaccessible.
[ https://issues.apache.org/jira/browse/HBASE-11419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178782#comment-14178782 ] Lars Hofhansl commented on HBASE-11419: --- Interesting. A flush will remove anything expired by TTL, thus producing possibly empty HFiles. I'll try produce a unittests for this. After increasing TTL value of a hbase table having pre-split regions and decreasing TTL value, table becomes inaccessible. -- Key: HBASE-11419 URL: https://issues.apache.org/jira/browse/HBASE-11419 Project: HBase Issue Type: Bug Components: HFile Affects Versions: 0.94.6 Environment: Linux x86_64 Reporter: Prabhu Joseph Priority: Blocker Fix For: 0.94.6 Attachments: HBaseExporter.java, account.csv Original Estimate: 96h Remaining Estimate: 96h After increasing and decreasing the TTL value of a Hbase Table , table gets inaccessible. Scan table not working. Scan in hbase shell throws java.lang.IllegalStateException: Block index not loaded at com.google.common.base.Preconditions.checkState(Preconditions.java:145) at org.apache.hadoop.hbase.io.hfile.HFileReaderV1.blockContainingKey(HFileReaderV1.java:181) at org.apache.hadoop.hbase.io.hfile.HFileReaderV1$AbstractScannerV1.seekTo(HFileReaderV1.java:426) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:226) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:145) at org.apache.hadoop.hbase.regionserver.StoreScanner.init(StoreScanner.java:131) at org.apache.hadoop.hbase.regionserver.Store.getScanner(Store.java:2015) at org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.init(HRegion.java:3706) at org.apache.hadoop.hbase.regionserver.HRegion.instantiateRegionScanner(HRegion.java:1761) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1753) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1730) at org.apache.hadoop.hbase.regionserver.HRegionServer.openScanner(HRegionServer.java:2409) at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:320) at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1426) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11419) After increasing TTL value of a hbase table having pre-split regions and decreasing TTL value, table becomes inaccessible.
[
https://issues.apache.org/jira/browse/HBASE-11419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178786#comment-14178786
]
Lars Hofhansl commented on HBASE-11419:
---
{{at
org.apache.hadoop.hbase.io.hfile.HFileReaderV1.blockContainingKey(HFileReaderV1.java:181)}}
is interesting. Looks like it cannot determine whether to use to reader v1 or
v2 and defaults to v1.
After increasing TTL value of a hbase table having pre-split regions and
decreasing TTL value, table becomes inaccessible.
--
Key: HBASE-11419
URL: https://issues.apache.org/jira/browse/HBASE-11419
Project: HBase
Issue Type: Bug
Components: HFile
Affects Versions: 0.94.6
Environment: Linux x86_64
Reporter: Prabhu Joseph
Priority: Blocker
Fix For: 0.94.6
Attachments: HBaseExporter.java, account.csv
Original Estimate: 96h
Remaining Estimate: 96h
After increasing and decreasing the TTL value of a Hbase Table , table gets
inaccessible. Scan table not working.
Scan in hbase shell throws
java.lang.IllegalStateException: Block index not loaded
at com.google.common.base.Preconditions.checkState(Preconditions.java:145)
at
org.apache.hadoop.hbase.io.hfile.HFileReaderV1.blockContainingKey(HFileReaderV1.java:181)
at
org.apache.hadoop.hbase.io.hfile.HFileReaderV1$AbstractScannerV1.seekTo(HFileReaderV1.java:426)
at
org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:226)
at
org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:145)
at
org.apache.hadoop.hbase.regionserver.StoreScanner.init(StoreScanner.java:131)
at org.apache.hadoop.hbase.regionserver.Store.getScanner(Store.java:2015)
at
org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.init(HRegion.java:3706)
at
org.apache.hadoop.hbase.regionserver.HRegion.instantiateRegionScanner(HRegion.java:1761)
at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1753)
at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1730)
at
org.apache.hadoop.hbase.regionserver.HRegionServer.openScanner(HRegionServer.java:2409)
at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:320)
at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1426)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-12312) Another couple of createTable race conditions
Dima Spivak created HBASE-12312: --- Summary: Another couple of createTable race conditions Key: HBASE-12312 URL: https://issues.apache.org/jira/browse/HBASE-12312 Project: HBase Issue Type: Bug Reporter: Dima Spivak Assignee: Dima Spivak Found a couple more failing tests in TestAccessController and TestScanEarlyTermination caused by my favorite race condition. :) Will post a patch in a second. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12312) Another couple of createTable race conditions
[ https://issues.apache.org/jira/browse/HBASE-12312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak updated HBASE-12312: Status: Patch Available (was: Open) Another couple of createTable race conditions - Key: HBASE-12312 URL: https://issues.apache.org/jira/browse/HBASE-12312 Project: HBase Issue Type: Bug Reporter: Dima Spivak Assignee: Dima Spivak Attachments: HBASE-12312_master_v1.patch Found a couple more failing tests in TestAccessController and TestScanEarlyTermination caused by my favorite race condition. :) Will post a patch in a second. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12312) Another couple of createTable race conditions
[ https://issues.apache.org/jira/browse/HBASE-12312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak updated HBASE-12312: Attachment: HBASE-12312_master_v1.patch Another couple of createTable race conditions - Key: HBASE-12312 URL: https://issues.apache.org/jira/browse/HBASE-12312 Project: HBase Issue Type: Bug Reporter: Dima Spivak Assignee: Dima Spivak Attachments: HBASE-12312_master_v1.patch Found a couple more failing tests in TestAccessController and TestScanEarlyTermination caused by my favorite race condition. :) Will post a patch in a second. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12312) Another couple of createTable race conditions
[ https://issues.apache.org/jira/browse/HBASE-12312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178805#comment-14178805 ] Elliott Clark commented on HBASE-12312: --- Should we just remove wait until table enabled? Another couple of createTable race conditions - Key: HBASE-12312 URL: https://issues.apache.org/jira/browse/HBASE-12312 Project: HBase Issue Type: Bug Reporter: Dima Spivak Assignee: Dima Spivak Attachments: HBASE-12312_master_v1.patch Found a couple more failing tests in TestAccessController and TestScanEarlyTermination caused by my favorite race condition. :) Will post a patch in a second. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12312) Another couple of createTable race conditions
[ https://issues.apache.org/jira/browse/HBASE-12312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178812#comment-14178812 ] Dima Spivak commented on HBASE-12312: - Well I think there is a case for that (some tests disable a table, do something, and then need to wait for it get enabled again). In general, though, HBA#createTable should be followed by HBTU#waitUntilAllRegionsAssigned. Another couple of createTable race conditions - Key: HBASE-12312 URL: https://issues.apache.org/jira/browse/HBASE-12312 Project: HBase Issue Type: Bug Reporter: Dima Spivak Assignee: Dima Spivak Attachments: HBASE-12312_master_v1.patch Found a couple more failing tests in TestAccessController and TestScanEarlyTermination caused by my favorite race condition. :) Will post a patch in a second. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12286) [shell] Add server/cluster online load of configuration changes
[ https://issues.apache.org/jira/browse/HBASE-12286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack updated HBASE-12286: -- Resolution: Fixed Fix Version/s: 2.0.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to branch-1+. Thanks for nice feature port [~manukranthk] [shell] Add server/cluster online load of configuration changes --- Key: HBASE-12286 URL: https://issues.apache.org/jira/browse/HBASE-12286 Project: HBase Issue Type: New Feature Components: shell Reporter: stack Assignee: Manukranth Kolloju Fix For: 2.0.0, 0.99.2 Attachments: 0001-Add-doc-to-the-refguide-change-command-names-to-drop.patch, 0001-Adding-shell-methods-for-Admin.updateConfiguration.patch, 0001-HBASE-12286-Adding-HBase-Admin-method-for-updating-c.patch Add new loadConfig and loadConfig ServerName verbs to shell to expose new online loading of config changes. This is last piece of a forward port of 0.89fb dynamic config feature done by [~manukranthk] I'll do this last bit if no one else takes it up. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-12312) Another couple of createTable race conditions
[ https://issues.apache.org/jira/browse/HBASE-12312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dima Spivak updated HBASE-12312: Attachment: HBASE-12312_master_v2.patch Oops, forgot a handful of cases in my patch. Trying again; sorry for the noise. Another couple of createTable race conditions - Key: HBASE-12312 URL: https://issues.apache.org/jira/browse/HBASE-12312 Project: HBase Issue Type: Bug Reporter: Dima Spivak Assignee: Dima Spivak Attachments: HBASE-12312_master_v1.patch, HBASE-12312_master_v2.patch Found a couple more failing tests in TestAccessController and TestScanEarlyTermination caused by my favorite race condition. :) Will post a patch in a second. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12301) user_permission command does not show global permissions
[
https://issues.apache.org/jira/browse/HBASE-12301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178821#comment-14178821
]
Srikanth Srungarapu commented on HBASE-12301:
-
Patch looks good to me. Is the change from
AccessControlConstants.OP_ATTRIBUTE_ACL to acl intentional?
{code}
+ public static final TableName ACL_TABLE_NAME =
+ TableName.valueOf(NamespaceDescriptor.SYSTEM_NAMESPACE_NAME_STR, acl);
private static HTable getAclTable(Configuration conf) throws IOException {
-TableName aclTableName =
-TableName.valueOf(NamespaceDescriptor.SYSTEM_NAMESPACE_NAME_STR,
-AccessControlConstants.OP_ATTRIBUTE_ACL);
{code}
user_permission command does not show global permissions
Key: HBASE-12301
URL: https://issues.apache.org/jira/browse/HBASE-12301
Project: HBase
Issue Type: Bug
Components: security, shell
Affects Versions: 0.98.4, 2.0.0
Reporter: Jerry He
Assignee: Matteo Bertozzi
Attachments: HBASE-12301-v0.patch
It seems that since 0,98 or later, the shell command does not show global
permission anymore, even requested by user with the right privilege.
{code}
hbase(main):004:0 user_permission
UserTable,Family,Qualifier:Permission
hbase default,table1,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table1,,: [Permission:
actions=READ,WRITE]
hbase default,table2,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table2,,: [Permission:
actions=READ,WRITE]
{code}
I recall in the older versions, global permissions were shown as permissions
on the hbase:acl table.
Anyway we need a way to show the global permissions as part of
user_permission request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12301) user_permission command does not show global permissions
[
https://issues.apache.org/jira/browse/HBASE-12301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178824#comment-14178824
]
Hadoop QA commented on HBASE-12301:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12676073/HBASE-12301-v0.patch
against trunk revision .
ATTACHMENT ID: 12676073
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{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 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/11418//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11418//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11418//artifact/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11418//artifact/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11418//artifact/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11418//artifact/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11418//artifact/patchprocess/newPatchFindbugsWarningshbase-rest.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11418//artifact/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11418//artifact/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11418//artifact/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11418//artifact/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/11418//artifact/patchprocess/newPatchFindbugsWarningshbase-annotations.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/11418//console
This message is automatically generated.
user_permission command does not show global permissions
Key: HBASE-12301
URL: https://issues.apache.org/jira/browse/HBASE-12301
Project: HBase
Issue Type: Bug
Components: security, shell
Affects Versions: 0.98.4, 2.0.0
Reporter: Jerry He
Assignee: Matteo Bertozzi
Attachments: HBASE-12301-v0.patch
It seems that since 0,98 or later, the shell command does not show global
permission anymore, even requested by user with the right privilege.
{code}
hbase(main):004:0 user_permission
UserTable,Family,Qualifier:Permission
hbase default,table1,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table1,,: [Permission:
actions=READ,WRITE]
hbase default,table2,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table2,,: [Permission:
actions=READ,WRITE]
{code}
I recall in the older versions, global permissions were shown as permissions
on the hbase:acl table.
Anyway we need a way to show the global permissions as part of
user_permission request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12294) Can't build the docs after the hbase-checkstyle module was added
[
https://issues.apache.org/jira/browse/HBASE-12294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178823#comment-14178823
]
Elliott Clark commented on HBASE-12294:
---
Seems good. Let me commit the addendum patch here so that I can clean up my
mess that's blocking people.
Can't build the docs after the hbase-checkstyle module was added
Key: HBASE-12294
URL: https://issues.apache.org/jira/browse/HBASE-12294
Project: HBase
Issue Type: Bug
Components: build
Reporter: Misty Stanley-Jones
Assignee: Elliott Clark
Priority: Blocker
Fix For: 2.0.0, 0.98.8, 0.99.2
Attachments: 0001-HBASE-12294-Addendum.patch,
0001-HBASE-12294-Fix-site-generation.patch, HBASE-12294.patch
Since the 15th, I have not been able to build the docs. I get these errors:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on project
hbase-checkstyle: Missing distribution management in project HBase -
Checkstyle (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT) - [Help 1]
{code}
{code}
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-site-plugin:3.3:stage (default-cli) on
project hbase-checkstyle: Missing distribution management in project HBase -
Checkstyle (org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:108)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:76)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:116)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:361)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:157)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by: org.apache.maven.plugin.MojoExecutionException: Missing
distribution management in project HBase - Checkstyle
(org.apache.hbase:hbase-checkstyle:2.0.0-SNAPSHOT)
at
org.apache.maven.plugins.site.AbstractDeployMojo.getSite(AbstractDeployMojo.java:762)
at
org.apache.maven.plugins.site.AbstractDeployMojo.getDeployModuleDirectory(AbstractDeployMojo.java:249)
at
org.apache.maven.plugins.site.AbstractDeployMojo.deploy(AbstractDeployMojo.java:320)
at
org.apache.maven.plugins.site.AbstractDeployMojo.deployTo(AbstractDeployMojo.java:281)
at
org.apache.maven.plugins.site.AbstractDeployMojo.execute(AbstractDeployMojo.java:163)
at org.apache.maven.plugins.site.SiteStageMojo.execute(SiteStageMojo.java:75)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:133)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 19 more
{code}
I'm able to resolve it by adding the attached patch to the POM. [~eclark], is
there a specific reason you didn't use inheritance in the checkstyles module?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-12301) user_permission command does not show global permissions
[
https://issues.apache.org/jira/browse/HBASE-12301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178826#comment-14178826
]
Matteo Bertozzi commented on HBASE-12301:
-
yes, intentional. because OP_ATTRIBUTE_ACL is not the acl table name but the
tag name of the cell acls. It is just a coincidence that the name is the same.
user_permission command does not show global permissions
Key: HBASE-12301
URL: https://issues.apache.org/jira/browse/HBASE-12301
Project: HBase
Issue Type: Bug
Components: security, shell
Affects Versions: 0.98.4, 2.0.0
Reporter: Jerry He
Assignee: Matteo Bertozzi
Attachments: HBASE-12301-v0.patch
It seems that since 0,98 or later, the shell command does not show global
permission anymore, even requested by user with the right privilege.
{code}
hbase(main):004:0 user_permission
UserTable,Family,Qualifier:Permission
hbase default,table1,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table1,,: [Permission:
actions=READ,WRITE]
hbase default,table2,,: [Permission:
actions=READ,WRITE,EXEC,CREATE,ADMIN]
user2 default,table2,,: [Permission:
actions=READ,WRITE]
{code}
I recall in the older versions, global permissions were shown as permissions
on the hbase:acl table.
Anyway we need a way to show the global permissions as part of
user_permission request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11419) After increasing TTL value of a hbase table having pre-split regions and decreasing TTL value, table becomes inaccessible.
[ https://issues.apache.org/jira/browse/HBASE-11419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178831#comment-14178831 ] Lars Hofhansl commented on HBASE-11419: --- [~Prabhu Joseph], does this only happen with a distributed cluster, or also again a cluster in local mode? After increasing TTL value of a hbase table having pre-split regions and decreasing TTL value, table becomes inaccessible. -- Key: HBASE-11419 URL: https://issues.apache.org/jira/browse/HBASE-11419 Project: HBase Issue Type: Bug Components: HFile Affects Versions: 0.94.6 Environment: Linux x86_64 Reporter: Prabhu Joseph Priority: Blocker Fix For: 0.94.6 Attachments: HBaseExporter.java, account.csv Original Estimate: 96h Remaining Estimate: 96h After increasing and decreasing the TTL value of a Hbase Table , table gets inaccessible. Scan table not working. Scan in hbase shell throws java.lang.IllegalStateException: Block index not loaded at com.google.common.base.Preconditions.checkState(Preconditions.java:145) at org.apache.hadoop.hbase.io.hfile.HFileReaderV1.blockContainingKey(HFileReaderV1.java:181) at org.apache.hadoop.hbase.io.hfile.HFileReaderV1$AbstractScannerV1.seekTo(HFileReaderV1.java:426) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:226) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:145) at org.apache.hadoop.hbase.regionserver.StoreScanner.init(StoreScanner.java:131) at org.apache.hadoop.hbase.regionserver.Store.getScanner(Store.java:2015) at org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.init(HRegion.java:3706) at org.apache.hadoop.hbase.regionserver.HRegion.instantiateRegionScanner(HRegion.java:1761) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1753) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1730) at org.apache.hadoop.hbase.regionserver.HRegionServer.openScanner(HRegionServer.java:2409) at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:320) at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1426) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11419) After increasing TTL value of a hbase table having pre-split regions and decreasing TTL value, table becomes inaccessible.
[ https://issues.apache.org/jira/browse/HBASE-11419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178848#comment-14178848 ] Lars Hofhansl commented on HBASE-11419: --- I ran this in 0.94.24 against an HBase in local mode, and it worked fine. After increasing TTL value of a hbase table having pre-split regions and decreasing TTL value, table becomes inaccessible. -- Key: HBASE-11419 URL: https://issues.apache.org/jira/browse/HBASE-11419 Project: HBase Issue Type: Bug Components: HFile Affects Versions: 0.94.6 Environment: Linux x86_64 Reporter: Prabhu Joseph Priority: Blocker Fix For: 0.94.6 Attachments: HBaseExporter.java, account.csv Original Estimate: 96h Remaining Estimate: 96h After increasing and decreasing the TTL value of a Hbase Table , table gets inaccessible. Scan table not working. Scan in hbase shell throws java.lang.IllegalStateException: Block index not loaded at com.google.common.base.Preconditions.checkState(Preconditions.java:145) at org.apache.hadoop.hbase.io.hfile.HFileReaderV1.blockContainingKey(HFileReaderV1.java:181) at org.apache.hadoop.hbase.io.hfile.HFileReaderV1$AbstractScannerV1.seekTo(HFileReaderV1.java:426) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:226) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:145) at org.apache.hadoop.hbase.regionserver.StoreScanner.init(StoreScanner.java:131) at org.apache.hadoop.hbase.regionserver.Store.getScanner(Store.java:2015) at org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.init(HRegion.java:3706) at org.apache.hadoop.hbase.regionserver.HRegion.instantiateRegionScanner(HRegion.java:1761) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1753) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1730) at org.apache.hadoop.hbase.regionserver.HRegionServer.openScanner(HRegionServer.java:2409) at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:320) at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1426) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12308) Fix typo in hbase-rest profile name
[ https://issues.apache.org/jira/browse/HBASE-12308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178859#comment-14178859 ] Hudson commented on HBASE-12308: FAILURE: Integrated in HBase-0.98 #618 (See [https://builds.apache.org/job/HBase-0.98/618/]) HBASE-12308 Fix typo in hbase-rest profile name (Solomon Duskis) (stack: rev f1f54f60e213897b4a2b5b3daf9782fe5057ee8d) * hbase-rest/pom.xml Fix typo in hbase-rest profile name --- Key: HBASE-12308 URL: https://issues.apache.org/jira/browse/HBASE-12308 Project: HBase Issue Type: Bug Affects Versions: 2.0.0, 0.99.2 Reporter: Solomon Duskis Assignee: Solomon Duskis Priority: Minor Fix For: 2.0.0, 0.98.8, 0.99.2 Attachments: HBASE-12308.patch Change skipRestTets to skipRestTests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-11419) After increasing TTL value of a hbase table having pre-split regions and decreasing TTL value, table becomes inaccessible.
[ https://issues.apache.org/jira/browse/HBASE-11419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14178860#comment-14178860 ] Lars Hofhansl commented on HBASE-11419: --- Ran the same against a 0.94.6 HBase in local mode. Also works fine. I can't easily stand up an actual cluster right now. I tried a unittest against a minicluster in 0.94.24, which also worked fine. After increasing TTL value of a hbase table having pre-split regions and decreasing TTL value, table becomes inaccessible. -- Key: HBASE-11419 URL: https://issues.apache.org/jira/browse/HBASE-11419 Project: HBase Issue Type: Bug Components: HFile Affects Versions: 0.94.6 Environment: Linux x86_64 Reporter: Prabhu Joseph Priority: Blocker Fix For: 0.94.6 Attachments: HBaseExporter.java, account.csv Original Estimate: 96h Remaining Estimate: 96h After increasing and decreasing the TTL value of a Hbase Table , table gets inaccessible. Scan table not working. Scan in hbase shell throws java.lang.IllegalStateException: Block index not loaded at com.google.common.base.Preconditions.checkState(Preconditions.java:145) at org.apache.hadoop.hbase.io.hfile.HFileReaderV1.blockContainingKey(HFileReaderV1.java:181) at org.apache.hadoop.hbase.io.hfile.HFileReaderV1$AbstractScannerV1.seekTo(HFileReaderV1.java:426) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seekAtOrAfter(StoreFileScanner.java:226) at org.apache.hadoop.hbase.regionserver.StoreFileScanner.seek(StoreFileScanner.java:145) at org.apache.hadoop.hbase.regionserver.StoreScanner.init(StoreScanner.java:131) at org.apache.hadoop.hbase.regionserver.Store.getScanner(Store.java:2015) at org.apache.hadoop.hbase.regionserver.HRegion$RegionScannerImpl.init(HRegion.java:3706) at org.apache.hadoop.hbase.regionserver.HRegion.instantiateRegionScanner(HRegion.java:1761) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1753) at org.apache.hadoop.hbase.regionserver.HRegion.getScanner(HRegion.java:1730) at org.apache.hadoop.hbase.regionserver.HRegionServer.openScanner(HRegionServer.java:2409) at sun.reflect.GeneratedMethodAccessor56.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.hadoop.hbase.ipc.WritableRpcEngine$Server.call(WritableRpcEngine.java:320) at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1426) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
