[jira] [Commented] (HBASE-13537) Change the admin interface for async operations to return Future.
[ https://issues.apache.org/jira/browse/HBASE-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14512920#comment-14512920 ] Matteo Bertozzi commented on HBASE-13537: - i'm not good with methods comment so I'll let you decide this. in theory if we have the comment on the Admin interface it is not needed in HBaseAdmin (because you are using @Override), so we can remove the comments on the HBaseAdmin side, but the comments on the HBaseAdmin side for v2 version are better then the one we have in admin for async() because they explain the future stuff, so you should copy/paste them in Admin replacing the ones we have). I'm +1 on the patch, the decision on comments is up to you Change the admin interface for async operations to return Future. - Key: HBASE-13537 URL: https://issues.apache.org/jira/browse/HBASE-13537 Project: HBase Issue Type: Sub-task Components: proc-v2 Affects Versions: 2.0.0 Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Attachments: HBASE-13537.patch, HBASE-13537.patch, HBASE-13537.patch At the moment, the async operations are returning void. This task aims to change the return type to Future and remove the aysnc wrapper methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13537) Change the admin interface for async operations to return Future.
[
https://issues.apache.org/jira/browse/HBASE-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14512946#comment-14512946
]
Hadoop QA commented on HBASE-13537:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12728209/HBASE-13537.patch
against master branch at commit cd83d39fb4f50db901b699ba5470b5f709c95c69.
ATTACHMENT ID: 12728209
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.1 2.5.2 2.6.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn 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/13818//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13818//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/13818//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/13818//console
This message is automatically generated.
Change the admin interface for async operations to return Future.
-
Key: HBASE-13537
URL: https://issues.apache.org/jira/browse/HBASE-13537
Project: HBase
Issue Type: Sub-task
Components: proc-v2
Affects Versions: 2.0.0
Reporter: Srikanth Srungarapu
Assignee: Srikanth Srungarapu
Attachments: HBASE-13537.patch, HBASE-13537.patch, HBASE-13537.patch
At the moment, the async operations are returning void. This task aims to
change the return type to Future and remove the aysnc wrapper methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13566) MetaLogRoller get error wal.ProtobufLogWriter: Got IOException while writing trailer
[ https://issues.apache.org/jira/browse/HBASE-13566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14512942#comment-14512942 ] dirk.zhang commented on HBASE-13566: what's this mean?? I use a conf named hbase.regionserver.logroll.errors.tolerated to ignore the problem,but I want solve this problem. should I send a mail instead of pushing the problem in there MetaLogRoller get error wal.ProtobufLogWriter: Got IOException while writing trailer - Key: HBASE-13566 URL: https://issues.apache.org/jira/browse/HBASE-13566 Project: HBase Issue Type: Bug Components: hbase Affects Versions: 0.98.1 Environment: hadoop2.3.0 Reporter: dirk.zhang As hbase run MetaLogRoller thread for writting meta hlog, I got below error ERROR [RS_OPEN_META-xxx:60020-0-MetaLogRoller] wal.ProtobufLogWriter: Got IOException while writing trailer java.io.IOException: Failing write. Tried pipeline recovery 5 times without success. at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.processDatanodeError(DFSOutputStream.java:918) at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:486) 2015-04-25 19:52:05,463 ERROR [RS_OPEN_META-host152:60020-0-MetaLogRoller] wal.FSHLog: Failed close of HLog writer java.io.IOException: Failing write. Tried pipeline recovery 5 times without success. at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.processDatanodeError(DFSOutputStream.java:918) at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:486) 2015-04-25 19:52:05,463 FATAL [RS_OPEN_META-host152:60020-0-MetaLogRoller] regionserver.HRegionServer: ABORTING region server host152,60020,1429927886571: Failed log close in log roller org.apache.hadoop.hbase.regionserver.wal.FailedLogCloseException: #1429959124806 at org.apache.hadoop.hbase.regionserver.wal.FSHLog.cleanupCurrentWriter(FSHLog.java:777) at org.apache.hadoop.hbase.regionserver.wal.FSHLog.rollWriter(FSHLog.java:565) at org.apache.hadoop.hbase.regionserver.LogRoller.run(LogRoller.java:97) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Failing write. Tried pipeline recovery 5 times without success. at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.processDatanodeError(DFSOutputStream.java:918) at org.apache.hadoop.hdfs.DFSOutputStream$DataStreamer.run(DFSOutputStream.java:486) note: I hava checked namenode log, there is no error,just close the write socket and hadoop and hbase file is all fine -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13568) Make Waiter class a public API.
[
https://issues.apache.org/jira/browse/HBASE-13568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14512945#comment-14512945
]
Hadoop QA commented on HBASE-13568:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12728204/HBASE-13568.patch
against master branch at commit cd83d39fb4f50db901b699ba5470b5f709c95c69.
ATTACHMENT ID: 12728204
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 85 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.1 2.5.2 2.6.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
1903 checkstyle errors (more than the master's current 1900 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:
+ * Wrapper method for {@link WaiterForTesting#waitFor(Configuration,
long, long, boolean, Predicate)}.
+ public WaiterForTesting.PredicateIOException predicateTableAvailable(final
TableName tableName) {
+WaiterForTesting.waitFor(HTU.getConfiguration(), 1000, new
WaiterForTesting.PredicateException() {
+WaiterForTesting.waitFor(HTU.getConfiguration(), 1000, new
WaiterForTesting.PredicateException() {
+ WaiterForTesting.waitFor(HTU.getConfiguration(), 9, new
WaiterForTesting.PredicateException() {
{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/13817//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13817//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/13817//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13817//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/13817//console
This message is automatically generated.
Make Waiter class a public API.
---
Key: HBASE-13568
URL: https://issues.apache.org/jira/browse/HBASE-13568
Project: HBase
Issue Type: Task
Reporter: Srikanth Srungarapu
Assignee: Srikanth Srungarapu
Priority: Minor
Attachments: HBASE-13568.patch
During ProcV2 code reviews, it is suggested that Waiter class is useful
enough to make it a public API. This change decomposes the existing Waiter
class into two classes, one for public use and the other exclusively for the
internal testing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13546) NPE on region server status page if all masters are down
[ https://issues.apache.org/jira/browse/HBASE-13546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14512916#comment-14512916 ] Hudson commented on HBASE-13546: SUCCESS: Integrated in HBase-0.98 #966 (See [https://builds.apache.org/job/HBase-0.98/966/]) HBASE-13546 handle nulls in MasterAddressTracker when there is no master active. (busbey: rev 0f59698f25235dcb58ac14b1dbb0dacac62fc114) * hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestMasterAddressTracker.java * hbase-client/src/main/java/org/apache/hadoop/hbase/zookeeper/MasterAddressTracker.java NPE on region server status page if all masters are down Key: HBASE-13546 URL: https://issues.apache.org/jira/browse/HBASE-13546 Project: HBase Issue Type: Bug Components: regionserver Reporter: Sean Busbey Assignee: Sean Busbey Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.13, 1.2.0 Attachments: HBASE-13546-0.98.1.patch.txt, HBASE-13546.1.patch.txt, HBASE-13546.1.patch.txt while trying to debug a cluster with all masters down, I noticed going to the region server status page failed with NPE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (HBASE-13344) Add enforcer rule that matches our JDK support statement
[ https://issues.apache.org/jira/browse/HBASE-13344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Warhaftig reassigned HBASE-13344: -- Assignee: Matt Warhaftig Add enforcer rule that matches our JDK support statement Key: HBASE-13344 URL: https://issues.apache.org/jira/browse/HBASE-13344 Project: HBase Issue Type: Improvement Components: build Affects Versions: 2.0.0 Reporter: Sean Busbey Assignee: Matt Warhaftig Priority: Minor Labels: beginner, maven Fix For: 2.0.0 Attachments: HBASE-13344-master.patch The [ref guide gives a list of JDKs that we expect our hbase versions to work with at runtime|http://hbase.apache.org/book.html#basic.prerequisites]. Let's add in the extra-enforcer-rules mojo and start using [the bytecode version rule|http://mojo.codehaus.org/extra-enforcer-rules/enforceBytecodeVersion.html] to make sure that the result of our builds on a given branch won't fail out because of a misconfigured target jdk version (or a dependency that targets a later jdk). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13358) Upgrade VisibilityClient API to accept Connection object.
[
https://issues.apache.org/jira/browse/HBASE-13358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Warhaftig updated HBASE-13358:
---
Fix Version/s: 2.0.0
Assignee: Matt Warhaftig
Status: Patch Available (was: Open)
Attached patch 'HBASE-13358.patch' adds VisibilityClient methods that allow
connection to be passed and deprecates existing configuration parameter
methods. Associated JUnit tests are updated to use new methods. Please
double-check changes as HBase security logic was modified.
Upgrade VisibilityClient API to accept Connection object.
-
Key: HBASE-13358
URL: https://issues.apache.org/jira/browse/HBASE-13358
Project: HBase
Issue Type: Improvement
Reporter: Srikanth Srungarapu
Assignee: Matt Warhaftig
Priority: Minor
Fix For: 2.0.0
From VisibilityClient class:
{code}
// TODO: Make it so caller passes in a Connection rather than have us do
this expensive
// setup each time. This class only used in test and shell at moment
though.
{code}
Basically, this is the VC's counterpart of HBASE-13171.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13358) Upgrade VisibilityClient API to accept Connection object.
[
https://issues.apache.org/jira/browse/HBASE-13358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Warhaftig updated HBASE-13358:
---
Attachment: HBASE-13358.patch
Upgrade VisibilityClient API to accept Connection object.
-
Key: HBASE-13358
URL: https://issues.apache.org/jira/browse/HBASE-13358
Project: HBase
Issue Type: Improvement
Reporter: Srikanth Srungarapu
Assignee: Matt Warhaftig
Priority: Minor
Fix For: 2.0.0
Attachments: HBASE-13358.patch
From VisibilityClient class:
{code}
// TODO: Make it so caller passes in a Connection rather than have us do
this expensive
// setup each time. This class only used in test and shell at moment
though.
{code}
Basically, this is the VC's counterpart of HBASE-13171.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13358) Upgrade VisibilityClient API to accept Connection object.
[
https://issues.apache.org/jira/browse/HBASE-13358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Warhaftig updated HBASE-13358:
---
Attachment: HBASE-13358_v2.patch
Attached updated patch 'HBASE-13358_v2.patch' corrects one VisibilityClient
Javadoc parameter name value and adds @Deprecated annotation tags where needed.
Upgrade VisibilityClient API to accept Connection object.
-
Key: HBASE-13358
URL: https://issues.apache.org/jira/browse/HBASE-13358
Project: HBase
Issue Type: Improvement
Reporter: Srikanth Srungarapu
Assignee: Matt Warhaftig
Priority: Minor
Fix For: 2.0.0
Attachments: HBASE-13358.patch, HBASE-13358_v2.patch
From VisibilityClient class:
{code}
// TODO: Make it so caller passes in a Connection rather than have us do
this expensive
// setup each time. This class only used in test and shell at moment
though.
{code}
Basically, this is the VC's counterpart of HBASE-13171.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13537) Change the admin interface for async operations to return Future.
[ https://issues.apache.org/jira/browse/HBASE-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Srungarapu updated HBASE-13537: Resolution: Fixed Fix Version/s: 2.0.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to master branch. Thanks for the reviews. Change the admin interface for async operations to return Future. - Key: HBASE-13537 URL: https://issues.apache.org/jira/browse/HBASE-13537 Project: HBase Issue Type: Sub-task Components: proc-v2 Affects Versions: 2.0.0 Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Fix For: 2.0.0 Attachments: HBASE-13537.patch, HBASE-13537.patch, HBASE-13537.patch, HBASE-13537_v2.patch At the moment, the async operations are returning void. This task aims to change the return type to Future and remove the aysnc wrapper methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13563) Add missing table owner to AC tests.
[ https://issues.apache.org/jira/browse/HBASE-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Srungarapu updated HBASE-13563: Resolution: Fixed Fix Version/s: 1.2.0 1.0.2 2.0.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed the fix. Thanks for the review. Add missing table owner to AC tests. Key: HBASE-13563 URL: https://issues.apache.org/jira/browse/HBASE-13563 Project: HBase Issue Type: Sub-task Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Priority: Minor Fix For: 2.0.0, 1.0.2, 1.2.0 Attachments: HBASE-13563.patch As per the description. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13554) Update book clarifying API stability guarantees
[ https://issues.apache.org/jira/browse/HBASE-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513341#comment-14513341 ] Misty Stanley-Jones commented on HBASE-13554: - Attempting to build the website now. Will update here when it's complete. Update book clarifying API stability guarantees --- Key: HBASE-13554 URL: https://issues.apache.org/jira/browse/HBASE-13554 Project: HBase Issue Type: Task Components: documentation Reporter: Josh Elser Assignee: Josh Elser Fix For: 2.0.0 Attachments: HBASE-13554.patch From the Clarifying interface evolution freedom in patch releases [thread|http://mail-archives.apache.org/mod_mbox/hbase-dev/201504.mbox/%3CCA%2BRK%3D_CkTUfa3nWPsy2A0PZt07h%3D1stP72rcazBrw5U0JFdgXA%40mail.gmail.com%3E] on dev@h.a.o Seems we have consensus that HBase uses Semantic Versioning isn't quite correct (or desired) at the moment. Update the documentation to make sure we're not misrepresenting any guarantees to users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13466) Document deprecations in 1.x - Part 1
[ https://issues.apache.org/jira/browse/HBASE-13466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513295#comment-14513295 ] Hudson commented on HBASE-13466: FAILURE: Integrated in HBase-1.1 #431 (See [https://builds.apache.org/job/HBase-1.1/431/]) HBASE-13466 Document deprecations in 1.x - Part 1 (Lars Francke) (ndimiduk: rev 918a0102837ae6ce65c6cc531663ce85bc992782) * hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTableInterface.java * hbase-client/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java * hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableSplit.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java * hbase-client/src/main/java/org/apache/hadoop/hbase/HTableDescriptor.java * hbase-client/src/main/java/org/apache/hadoop/hbase/HRegionInfo.java * hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java * hbase-client/src/main/java/org/apache/hadoop/hbase/ClusterStatus.java Document deprecations in 1.x - Part 1 - Key: HBASE-13466 URL: https://issues.apache.org/jira/browse/HBASE-13466 Project: HBase Issue Type: Sub-task Reporter: Lars Francke Assignee: Lars Francke Fix For: 2.0.0, 1.1.0, 1.2.0 Attachments: HBASE-13466-v1-branch-1.patch, HBASE-13466-v2-branch-1.patch, HBASE-13466-v3-branch-1.patch, HBASE-13466-v4-branch-1.patch, HBASE-13466.1.patch This documents deprecations for the following issues: * HBASE-6038 * HBASE-1502 * HBASE-5453 * HBASE-5357 * HBASE-9870 * HBASE-10870 * HBASE-12363 * HBASE-9508 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13149) HBase MR is broken on Hadoop 2.5+ Yarn
[
https://issues.apache.org/jira/browse/HBASE-13149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513294#comment-14513294
]
Hudson commented on HBASE-13149:
FAILURE: Integrated in HBase-1.1 #431 (See
[https://builds.apache.org/job/HBase-1.1/431/])
HBASE-13149 HBase MR is broken on Hadoop 2.5+ Yarn (Jerry He) (ndimiduk: rev
555679d8e607109368d0e03448c5fd2cf71b7bc0)
* pom.xml
HBase MR is broken on Hadoop 2.5+ Yarn
--
Key: HBASE-13149
URL: https://issues.apache.org/jira/browse/HBASE-13149
Project: HBase
Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0, 0.98.10.1
Reporter: Jerry He
Assignee: Jerry He
Priority: Blocker
Fix For: 2.0.0, 1.1.0, 1.2.0
Attachments: HBASE-13149-0.98.patch, HBASE-13149-master.patch,
jackson-core-asl-compat_report.html, jackson-jaxrs-compat_report.html,
jackson-mapper-asl-compat_report.html, jackson-xc-compat_report.html,
jackson_1.8_to_1.9_compat_report.html
Running the server MR tools is not working on Yarn version 2.5+.
Running org.apache.hadoop.hbase.mapreduce.Export:
{noformat}
Exception in thread main java.lang.NoSuchMethodError:
org.codehaus.jackson.map.ObjectMapper.setSerializationInclusion(Lorg/codehaus/jackson/map/annotate/JsonSerialize$Inclusion;)Lorg/codehaus/jackson/map/ObjectMapper;
at
org.apache.hadoop.yarn.webapp.YarnJacksonJaxbJsonProvider.configObjectMapper(YarnJacksonJaxbJsonProvider.java:59)
at
org.apache.hadoop.yarn.util.timeline.TimelineUtils.clinit(TimelineUtils.java:47)
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:166)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.serviceInit(ResourceMgrDelegate.java:102)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.init(ResourceMgrDelegate.java:96)
at org.apache.hadoop.mapred.YARNRunner.init(YARNRunner.java:112)
at
org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
at org.apache.hadoop.mapreduce.Cluster.init(Cluster.java:82)
at org.apache.hadoop.mapreduce.Cluster.init(Cluster.java:75)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1266)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1262)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
at org.apache.hadoop.mapreduce.Job.connect(Job.java:1261)
at org.apache.hadoop.mapreduce.Job.submit(Job.java:1290)
at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1314)
at org.apache.hadoop.hbase.mapreduce.Export.main(Export.java:189)
{noformat}
The problem seems to be the jackson jar version. HADOOP-10104 updated
jackson version to 1.9.13. YARN-2092 reported a problem as well.
HBase is using jackson 1.8.8. This version of the jar in the classpath seem
to cause the problem.
Should we upgrade to jackson 1.9.13?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13569) correct errors reported with mvn site
[ https://issues.apache.org/jira/browse/HBASE-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513302#comment-14513302 ] Gabor Liptak commented on HBASE-13569: -- When running with Java 8 http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html correct errors reported with mvn site - Key: HBASE-13569 URL: https://issues.apache.org/jira/browse/HBASE-13569 Project: HBase Issue Type: Bug Reporter: Gabor Liptak Priority: Minor There are a number of Javadoc errors reported when running mvn site. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13149) HBase MR is broken on Hadoop 2.5+ Yarn
[
https://issues.apache.org/jira/browse/HBASE-13149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513326#comment-14513326
]
Hudson commented on HBASE-13149:
FAILURE: Integrated in HBase-TRUNK #6415 (See
[https://builds.apache.org/job/HBase-TRUNK/6415/])
HBASE-13149 HBase MR is broken on Hadoop 2.5+ Yarn (Jerry He) (ndimiduk: rev
9ae023fcab15d0e628bcb21c40f4043890a1feb8)
* pom.xml
HBase MR is broken on Hadoop 2.5+ Yarn
--
Key: HBASE-13149
URL: https://issues.apache.org/jira/browse/HBASE-13149
Project: HBase
Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0, 0.98.10.1
Reporter: Jerry He
Assignee: Jerry He
Priority: Blocker
Fix For: 2.0.0, 1.1.0, 1.2.0
Attachments: HBASE-13149-0.98.patch, HBASE-13149-master.patch,
jackson-core-asl-compat_report.html, jackson-jaxrs-compat_report.html,
jackson-mapper-asl-compat_report.html, jackson-xc-compat_report.html,
jackson_1.8_to_1.9_compat_report.html
Running the server MR tools is not working on Yarn version 2.5+.
Running org.apache.hadoop.hbase.mapreduce.Export:
{noformat}
Exception in thread main java.lang.NoSuchMethodError:
org.codehaus.jackson.map.ObjectMapper.setSerializationInclusion(Lorg/codehaus/jackson/map/annotate/JsonSerialize$Inclusion;)Lorg/codehaus/jackson/map/ObjectMapper;
at
org.apache.hadoop.yarn.webapp.YarnJacksonJaxbJsonProvider.configObjectMapper(YarnJacksonJaxbJsonProvider.java:59)
at
org.apache.hadoop.yarn.util.timeline.TimelineUtils.clinit(TimelineUtils.java:47)
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:166)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.serviceInit(ResourceMgrDelegate.java:102)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.init(ResourceMgrDelegate.java:96)
at org.apache.hadoop.mapred.YARNRunner.init(YARNRunner.java:112)
at
org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
at org.apache.hadoop.mapreduce.Cluster.init(Cluster.java:82)
at org.apache.hadoop.mapreduce.Cluster.init(Cluster.java:75)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1266)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1262)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
at org.apache.hadoop.mapreduce.Job.connect(Job.java:1261)
at org.apache.hadoop.mapreduce.Job.submit(Job.java:1290)
at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1314)
at org.apache.hadoop.hbase.mapreduce.Export.main(Export.java:189)
{noformat}
The problem seems to be the jackson jar version. HADOOP-10104 updated
jackson version to 1.9.13. YARN-2092 reported a problem as well.
HBase is using jackson 1.8.8. This version of the jar in the classpath seem
to cause the problem.
Should we upgrade to jackson 1.9.13?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13466) Document deprecations in 1.x - Part 1
[ https://issues.apache.org/jira/browse/HBASE-13466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513327#comment-14513327 ] Hudson commented on HBASE-13466: FAILURE: Integrated in HBase-TRUNK #6415 (See [https://builds.apache.org/job/HBase-TRUNK/6415/]) HBASE-13466 Document deprecations in 1.x - Part 1 (Lars Francke) (ndimiduk: rev ba6ba16bc008e3b9bb8dc4b1674891e9e2313fc0) * hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableSplit.java * hbase-client/src/main/java/org/apache/hadoop/hbase/HRegionInfo.java * hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTableInterface.java * hbase-client/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java * hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java * hbase-client/src/main/java/org/apache/hadoop/hbase/HTableDescriptor.java * hbase-client/src/main/java/org/apache/hadoop/hbase/ClusterStatus.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java Document deprecations in 1.x - Part 1 - Key: HBASE-13466 URL: https://issues.apache.org/jira/browse/HBASE-13466 Project: HBase Issue Type: Sub-task Reporter: Lars Francke Assignee: Lars Francke Fix For: 2.0.0, 1.1.0, 1.2.0 Attachments: HBASE-13466-v1-branch-1.patch, HBASE-13466-v2-branch-1.patch, HBASE-13466-v3-branch-1.patch, HBASE-13466-v4-branch-1.patch, HBASE-13466.1.patch This documents deprecations for the following issues: * HBASE-6038 * HBASE-1502 * HBASE-5453 * HBASE-5357 * HBASE-9870 * HBASE-10870 * HBASE-12363 * HBASE-9508 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13359) Update ACL matrix to include table owner.
[ https://issues.apache.org/jira/browse/HBASE-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-13359: Component/s: documentation Update ACL matrix to include table owner. - Key: HBASE-13359 URL: https://issues.apache.org/jira/browse/HBASE-13359 Project: HBase Issue Type: Bug Components: documentation Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Priority: Minor Attachments: HBASE-13359.patch Looks like we allow table owner to truncate and modify table. We should update ACL matrix to reflect this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13564) Master MBeans are not published
[ https://issues.apache.org/jira/browse/HBASE-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513293#comment-14513293 ] Ted Yu commented on HBASE-13564: [~ndimiduk]: Please consider this to be included for hbase 1.1.0 Master MBeans are not published --- Key: HBASE-13564 URL: https://issues.apache.org/jira/browse/HBASE-13564 Project: HBase Issue Type: Bug Affects Versions: 1.0.1 Reporter: Ashish Singhi Assignee: Ashish Singhi Fix For: 2.0.0, 1.1.0, 1.0.2, 1.2.0 Attachments: HBASE-13564.patch Master MBeans are not published. For more details check the mailing thread on dev@h.a.o with subject How to retrieve master metrics from JMX client (http://osdir.com/ml/general/2015-04/msg29773.html) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13466) Document deprecations in 1.x - Part 1
[ https://issues.apache.org/jira/browse/HBASE-13466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513320#comment-14513320 ] Hudson commented on HBASE-13466: FAILURE: Integrated in HBase-1.2 #25 (See [https://builds.apache.org/job/HBase-1.2/25/]) HBASE-13466 Document deprecations in 1.x - Part 1 (Lars Francke) (ndimiduk: rev 566dfda5b79f0d0035c58b285cfab2fc54f3c8fb) * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableSplit.java * hbase-client/src/main/java/org/apache/hadoop/hbase/HTableDescriptor.java * hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTableInterface.java * hbase-client/src/main/java/org/apache/hadoop/hbase/client/HTable.java * hbase-client/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java * hbase-client/src/main/java/org/apache/hadoop/hbase/HRegionInfo.java * hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java * hbase-client/src/main/java/org/apache/hadoop/hbase/ClusterStatus.java * hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java Document deprecations in 1.x - Part 1 - Key: HBASE-13466 URL: https://issues.apache.org/jira/browse/HBASE-13466 Project: HBase Issue Type: Sub-task Reporter: Lars Francke Assignee: Lars Francke Fix For: 2.0.0, 1.1.0, 1.2.0 Attachments: HBASE-13466-v1-branch-1.patch, HBASE-13466-v2-branch-1.patch, HBASE-13466-v3-branch-1.patch, HBASE-13466-v4-branch-1.patch, HBASE-13466.1.patch This documents deprecations for the following issues: * HBASE-6038 * HBASE-1502 * HBASE-5453 * HBASE-5357 * HBASE-9870 * HBASE-10870 * HBASE-12363 * HBASE-9508 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13464) Remove deprecations for 2.0.0 - Part 1
[
https://issues.apache.org/jira/browse/HBASE-13464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513329#comment-14513329
]
Lars Francke commented on HBASE-13464:
--
I can't get precommit to run again for some reason. Andrew canceled the patch
once and so did I but nothing happened. Any idea on how to get this going?
Remove deprecations for 2.0.0 - Part 1
--
Key: HBASE-13464
URL: https://issues.apache.org/jira/browse/HBASE-13464
Project: HBase
Issue Type: Sub-task
Reporter: Lars Francke
Assignee: Lars Francke
Fix For: 2.0.0
Attachments: HBASE-13464.1.patch, HBASE-13464.2.patch
This removes deprecations for the following issues:
* HBASE-6038
* HBASE-1502
* HBASE-5453
* HBASE-5357
* HBASE-9870
* HBASE-10870
* HBASE-12363
* HBASE-9508
It introduces one new deprecation for
{{UnmodifyableHTableDescriptor#UnmodifyableHTableDescriptor()}} because that
depends on a deprecated constructor in {{HTableDescriptor}}. I've made the
constructor in question {{protected}} so both can be removed in 3.0.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13279) Add src/main/asciidoc/asciidoctor.css to RAT exclusion list in POM
[ https://issues.apache.org/jira/browse/HBASE-13279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Misty Stanley-Jones updated HBASE-13279: Hadoop Flags: Reviewed Add src/main/asciidoc/asciidoctor.css to RAT exclusion list in POM -- Key: HBASE-13279 URL: https://issues.apache.org/jira/browse/HBASE-13279 Project: HBase Issue Type: Bug Components: documentation Reporter: Andrew Purtell Assignee: Andrew Purtell Priority: Minor Fix For: 2.0.0 Attachments: 0001-Add-src-main-asciidoc-asciidoctor.css-to-RAT-exclusi.patch After copying back the latest doc updates from trunk to 0.98 branch for a release, the release audit failed due to src/main/asciidoc/asciidoctor.css, which is MIT licensed but only by reference. Exclude it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13359) Update ACL matrix to include table owner.
[ https://issues.apache.org/jira/browse/HBASE-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513340#comment-14513340 ] Misty Stanley-Jones commented on HBASE-13359: - +1 lgtm. Did you try building it locally? Update ACL matrix to include table owner. - Key: HBASE-13359 URL: https://issues.apache.org/jira/browse/HBASE-13359 Project: HBase Issue Type: Bug Components: documentation Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Priority: Minor Attachments: HBASE-13359.patch Looks like we allow table owner to truncate and modify table. We should update ACL matrix to reflect this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13358) Upgrade VisibilityClient API to accept Connection object.
[
https://issues.apache.org/jira/browse/HBASE-13358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513363#comment-14513363
]
Hadoop QA commented on HBASE-13358:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12728273/HBASE-13358_v2.patch
against master branch at commit ba6ba16bc008e3b9bb8dc4b1674891e9e2313fc0.
ATTACHMENT ID: 12728273
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 60 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.1 2.5.2 2.6.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.util.TestHBaseFsck
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/13821//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13821//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/13821//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/13821//console
This message is automatically generated.
Upgrade VisibilityClient API to accept Connection object.
-
Key: HBASE-13358
URL: https://issues.apache.org/jira/browse/HBASE-13358
Project: HBase
Issue Type: Improvement
Reporter: Srikanth Srungarapu
Assignee: Matt Warhaftig
Priority: Minor
Fix For: 2.0.0
Attachments: HBASE-13358.patch, HBASE-13358_v2.patch
From VisibilityClient class:
{code}
// TODO: Make it so caller passes in a Connection rather than have us do
this expensive
// setup each time. This class only used in test and shell at moment
though.
{code}
Basically, this is the VC's counterpart of HBASE-13171.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-11339) HBase MOB
[ https://issues.apache.org/jira/browse/HBASE-11339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513229#comment-14513229 ] Nick Dimiduk commented on HBASE-11339: -- Is there a branch/tag/sha that looks roughly like what you'd want to commit to branch-1.1? I'd like to add it to my jenkins rotations. Thanks. HBase MOB - Key: HBASE-11339 URL: https://issues.apache.org/jira/browse/HBASE-11339 Project: HBase Issue Type: Umbrella Components: regionserver, Scanners Affects Versions: 2.0.0 Reporter: Jingcheng Du Assignee: Jingcheng Du Fix For: hbase-11339 Attachments: HBase MOB Design-v2.pdf, HBase MOB Design-v3.pdf, HBase MOB Design-v4.pdf, HBase MOB Design-v5.pdf, HBase MOB Design.pdf, MOB user guide.docx, MOB user guide_v2.docx, MOB user guide_v3.docx, MOB user guide_v4.docx, MOB user guide_v5.docx, hbase-11339-in-dev.patch, hbase-11339.150417.patch, merge-150212.patch, merge.150212b.patch, merge.150212c.patch It's quite useful to save the medium binary data like images, documents into Apache HBase. Unfortunately directly saving the binary MOB(medium object) to HBase leads to a worse performance since the frequent split and compaction. In this design, the MOB data are stored in an more efficient way, which keeps a high write/read performance and guarantees the data consistency in Apache HBase. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13339) Update default Hadoop version to 2.6.0
[ https://issues.apache.org/jira/browse/HBASE-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513250#comment-14513250 ] Hudson commented on HBASE-13339: FAILURE: Integrated in HBase-1.1.0RC0-JDK7 #12 (See [https://builds.apache.org/job/HBase-1.1.0RC0-JDK7/12/]) HBASE-13339 Update default Hadoop version to 2.6.0 (ndimiduk: rev 56761d04e06e1e21a2b3257dd5989ba5e3240468) * pom.xml Update default Hadoop version to 2.6.0 -- Key: HBASE-13339 URL: https://issues.apache.org/jira/browse/HBASE-13339 Project: HBase Issue Type: Bug Components: build Affects Versions: 2.0.0, 1.1.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.1.0, 1.2.0 Attachments: HBASE-13339-v1.patch, HBASE-13339.patch Current default Hadoop version is getting a little long in the tooth. We should update to the latest version. The latest version is backwards compatible with 2.5.1's dfs and mr so this should be painless. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13339) Update default Hadoop version to 2.6.0
[ https://issues.apache.org/jira/browse/HBASE-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513258#comment-14513258 ] Hudson commented on HBASE-13339: FAILURE: Integrated in HBase-1.1.0RC0-JDK8 #10 (See [https://builds.apache.org/job/HBase-1.1.0RC0-JDK8/10/]) HBASE-13339 Update default Hadoop version to 2.6.0 (ndimiduk: rev 56761d04e06e1e21a2b3257dd5989ba5e3240468) * pom.xml Update default Hadoop version to 2.6.0 -- Key: HBASE-13339 URL: https://issues.apache.org/jira/browse/HBASE-13339 Project: HBase Issue Type: Bug Components: build Affects Versions: 2.0.0, 1.1.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.1.0, 1.2.0 Attachments: HBASE-13339-v1.patch, HBASE-13339.patch Current default Hadoop version is getting a little long in the tooth. We should update to the latest version. The latest version is backwards compatible with 2.5.1's dfs and mr so this should be painless. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13537) Change the admin interface for async operations to return Future.
[
https://issues.apache.org/jira/browse/HBASE-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513261#comment-14513261
]
Hadoop QA commented on HBASE-13537:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12728248/HBASE-13537_v2.patch
against master branch at commit cd83d39fb4f50db901b699ba5470b5f709c95c69.
ATTACHMENT ID: 12728248
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.1 2.5.2 2.6.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn 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/13820//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13820//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/13820//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/13820//console
This message is automatically generated.
Change the admin interface for async operations to return Future.
-
Key: HBASE-13537
URL: https://issues.apache.org/jira/browse/HBASE-13537
Project: HBase
Issue Type: Sub-task
Components: proc-v2
Affects Versions: 2.0.0
Reporter: Srikanth Srungarapu
Assignee: Srikanth Srungarapu
Attachments: HBASE-13537.patch, HBASE-13537.patch, HBASE-13537.patch,
HBASE-13537_v2.patch
At the moment, the async operations are returning void. This task aims to
change the return type to Future and remove the aysnc wrapper methods.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13537) Change the admin interface for async operations to return Future.
[ https://issues.apache.org/jira/browse/HBASE-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513168#comment-14513168 ] Srikanth Srungarapu commented on HBASE-13537: - Admin is public facing interface. I'm not gonna take any chances :). Uploaded the patch with the updated javadoc comments. Change the admin interface for async operations to return Future. - Key: HBASE-13537 URL: https://issues.apache.org/jira/browse/HBASE-13537 Project: HBase Issue Type: Sub-task Components: proc-v2 Affects Versions: 2.0.0 Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Attachments: HBASE-13537.patch, HBASE-13537.patch, HBASE-13537.patch, HBASE-13537_v2.patch At the moment, the async operations are returning void. This task aims to change the return type to Future and remove the aysnc wrapper methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13358) Upgrade VisibilityClient API to accept Connection object.
[
https://issues.apache.org/jira/browse/HBASE-13358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513175#comment-14513175
]
Hadoop QA commented on HBASE-13358:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12728241/HBASE-13358.patch
against master branch at commit cd83d39fb4f50db901b699ba5470b5f709c95c69.
ATTACHMENT ID: 12728241
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 73 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.1 2.5.2 2.6.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:red}-1 javadoc{color}. The javadoc tool appears to have generated 1
warning messages.
{color:red}-1 checkstyle{color}. The applied patch generated
1906 checkstyle errors (more than the master's current 1900 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/13819//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13819//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/13819//artifact/patchprocess/checkstyle-aggregate.html
Javadoc warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13819//artifact/patchprocess/patchJavadocWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/13819//console
This message is automatically generated.
Upgrade VisibilityClient API to accept Connection object.
-
Key: HBASE-13358
URL: https://issues.apache.org/jira/browse/HBASE-13358
Project: HBase
Issue Type: Improvement
Reporter: Srikanth Srungarapu
Assignee: Matt Warhaftig
Priority: Minor
Fix For: 2.0.0
Attachments: HBASE-13358.patch
From VisibilityClient class:
{code}
// TODO: Make it so caller passes in a Connection rather than have us do
this expensive
// setup each time. This class only used in test and shell at moment
though.
{code}
Basically, this is the VC's counterpart of HBASE-13171.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13339) Update default Hadoop version to 2.6.0
[ https://issues.apache.org/jira/browse/HBASE-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-13339: - Resolution: Fixed Fix Version/s: 1.2.0 1.1.0 2.0.0 Status: Resolved (was: Patch Available) Per discussions [0], [1], I've pushed this to branch-1.1+. Thanks [~eclark]. Mind giving us a nice release note summarizing the reasoning here? [0]: http://mail-archives.apache.org/mod_mbox/hbase-dev/201504.mbox/%3CCA+RK=_C6OJi=y_4xtmhjz2yusbmpd9tvvhnk_p9zmi_cahu...@mail.gmail.com%3E [1]: http://mail-archives.apache.org/mod_mbox/hbase-dev/201504.mbox/%3cCA+RK=_CkTUfa3nWPsy2A0PZt07h=1stp72rcazbrw5u0jfd...@mail.gmail.com%3e Update default Hadoop version to 2.6.0 -- Key: HBASE-13339 URL: https://issues.apache.org/jira/browse/HBASE-13339 Project: HBase Issue Type: Bug Components: build Affects Versions: 2.0.0, 1.1.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.1.0, 1.2.0 Attachments: HBASE-13339-v1.patch, HBASE-13339.patch Current default Hadoop version is getting a little long in the tooth. We should update to the latest version. The latest version is backwards compatible with 2.5.1's dfs and mr so this should be painless. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13149) HBase MR is broken on Hadoop 2.5+ Yarn
[
https://issues.apache.org/jira/browse/HBASE-13149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-13149:
-
Assignee: Jerry He
HBase MR is broken on Hadoop 2.5+ Yarn
--
Key: HBASE-13149
URL: https://issues.apache.org/jira/browse/HBASE-13149
Project: HBase
Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0, 0.98.10.1
Reporter: Jerry He
Assignee: Jerry He
Priority: Blocker
Fix For: 2.0.0, 1.1.0
Attachments: HBASE-13149-0.98.patch, HBASE-13149-master.patch,
jackson-core-asl-compat_report.html, jackson-jaxrs-compat_report.html,
jackson-mapper-asl-compat_report.html, jackson-xc-compat_report.html,
jackson_1.8_to_1.9_compat_report.html
Running the server MR tools is not working on Yarn version 2.5+.
Running org.apache.hadoop.hbase.mapreduce.Export:
{noformat}
Exception in thread main java.lang.NoSuchMethodError:
org.codehaus.jackson.map.ObjectMapper.setSerializationInclusion(Lorg/codehaus/jackson/map/annotate/JsonSerialize$Inclusion;)Lorg/codehaus/jackson/map/ObjectMapper;
at
org.apache.hadoop.yarn.webapp.YarnJacksonJaxbJsonProvider.configObjectMapper(YarnJacksonJaxbJsonProvider.java:59)
at
org.apache.hadoop.yarn.util.timeline.TimelineUtils.clinit(TimelineUtils.java:47)
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:166)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.serviceInit(ResourceMgrDelegate.java:102)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.init(ResourceMgrDelegate.java:96)
at org.apache.hadoop.mapred.YARNRunner.init(YARNRunner.java:112)
at
org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
at org.apache.hadoop.mapreduce.Cluster.init(Cluster.java:82)
at org.apache.hadoop.mapreduce.Cluster.init(Cluster.java:75)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1266)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1262)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
at org.apache.hadoop.mapreduce.Job.connect(Job.java:1261)
at org.apache.hadoop.mapreduce.Job.submit(Job.java:1290)
at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1314)
at org.apache.hadoop.hbase.mapreduce.Export.main(Export.java:189)
{noformat}
The problem seems to be the jackson jar version. HADOOP-10104 updated
jackson version to 1.9.13. YARN-2092 reported a problem as well.
HBase is using jackson 1.8.8. This version of the jar in the classpath seem
to cause the problem.
Should we upgrade to jackson 1.9.13?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13260) Bootstrap Tables for fun and profit
[ https://issues.apache.org/jira/browse/HBASE-13260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513204#comment-14513204 ] Nick Dimiduk commented on HBASE-13260: -- Where do we stand with this one. Clock is ticking on 1.1. Bootstrap Tables for fun and profit Key: HBASE-13260 URL: https://issues.apache.org/jira/browse/HBASE-13260 Project: HBase Issue Type: Bug Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: 2.0.0, 1.1.0 Attachments: hbase-13260_bench.patch, hbase-13260_prototype.patch Over at the ProcV2 discussions(HBASE-12439) and elsewhere I was mentioning an idea where we may want to use regular old regions to store/persist some data needed for HBase master to operate. We regularly use system tables for storing system data. acl, meta, namespace, quota are some examples. We also store the table state in meta now. Some data is persisted in zk only (replication peers and replication state, etc). We are moving away from zk as a permanent storage. As any self-respecting database does, we should store almost all of our data in HBase itself. However, we have an availability dependency between different kinds of data. For example all system tables need meta to be assigned first. All master operations need ns table to be assigned, etc. For at least two types of data, (1) procedure v2 states, (2) RS groups in HBASE-6721 we cannot depend on meta being assigned since assignment itself will depend on accessing this data. The solution in (1) is to implement a custom WAL format, and custom recover lease and WAL recovery. The solution in (2) is to have the table to store this data, but also cache it in zk for bootrapping initial assignments. For solving both of the above (and possible future use cases if any), I propose we add a boostrap table concept, which is: - A set of predefined tables hosted in a separate dir in HDFS. - A table is only 1 region, not splittable - Not assigned through regular assignment - Hosted only on 1 server (typically master) - Has a dedicated WAL. - A service does WAL recovery + fencing for these tables. This has the benefit of using a region to keep the data, but frees us to re-implement caching and we can use the same WAL / Memstore / Recovery mechanisms that are battle-tested. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13466) Document deprecations in 1.x - Part 1
[ https://issues.apache.org/jira/browse/HBASE-13466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Dimiduk updated HBASE-13466: - Resolution: Fixed Fix Version/s: 2.0.0 Status: Resolved (was: Patch Available) Pushed to branch-1.1+. Thanks [~lars_francke]. Document deprecations in 1.x - Part 1 - Key: HBASE-13466 URL: https://issues.apache.org/jira/browse/HBASE-13466 Project: HBase Issue Type: Sub-task Reporter: Lars Francke Assignee: Lars Francke Fix For: 2.0.0, 1.1.0, 1.2.0 Attachments: HBASE-13466-v1-branch-1.patch, HBASE-13466-v2-branch-1.patch, HBASE-13466-v3-branch-1.patch, HBASE-13466-v4-branch-1.patch, HBASE-13466.1.patch This documents deprecations for the following issues: * HBASE-6038 * HBASE-1502 * HBASE-5453 * HBASE-5357 * HBASE-9870 * HBASE-10870 * HBASE-12363 * HBASE-9508 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13537) Change the admin interface for async operations to return Future.
[ https://issues.apache.org/jira/browse/HBASE-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513262#comment-14513262 ] Matteo Bertozzi commented on HBASE-13537: - +1 on v2 Change the admin interface for async operations to return Future. - Key: HBASE-13537 URL: https://issues.apache.org/jira/browse/HBASE-13537 Project: HBase Issue Type: Sub-task Components: proc-v2 Affects Versions: 2.0.0 Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Attachments: HBASE-13537.patch, HBASE-13537.patch, HBASE-13537.patch, HBASE-13537_v2.patch At the moment, the async operations are returning void. This task aims to change the return type to Future and remove the aysnc wrapper methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13339) Update default Hadoop version to 2.6.0
[ https://issues.apache.org/jira/browse/HBASE-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513266#comment-14513266 ] Hudson commented on HBASE-13339: FAILURE: Integrated in HBase-TRUNK #6414 (See [https://builds.apache.org/job/HBase-TRUNK/6414/]) HBASE-13339 Update default Hadoop version to 2.6.0 (ndimiduk: rev 4d6dc38a70c57e5b7512533284024832e0f879dc) * pom.xml Update default Hadoop version to 2.6.0 -- Key: HBASE-13339 URL: https://issues.apache.org/jira/browse/HBASE-13339 Project: HBase Issue Type: Bug Components: build Affects Versions: 2.0.0, 1.1.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.1.0, 1.2.0 Attachments: HBASE-13339-v1.patch, HBASE-13339.patch Current default Hadoop version is getting a little long in the tooth. We should update to the latest version. The latest version is backwards compatible with 2.5.1's dfs and mr so this should be painless. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13339) Update default Hadoop version to 2.6.0
[ https://issues.apache.org/jira/browse/HBASE-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513275#comment-14513275 ] Hudson commented on HBASE-13339: FAILURE: Integrated in HBase-1.2 #24 (See [https://builds.apache.org/job/HBase-1.2/24/]) HBASE-13339 Update default Hadoop version to 2.6.0 (ndimiduk: rev c15862b8b1937c40c156de04ab406fa003817046) * pom.xml Update default Hadoop version to 2.6.0 -- Key: HBASE-13339 URL: https://issues.apache.org/jira/browse/HBASE-13339 Project: HBase Issue Type: Bug Components: build Affects Versions: 2.0.0, 1.1.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.1.0, 1.2.0 Attachments: HBASE-13339-v1.patch, HBASE-13339.patch Current default Hadoop version is getting a little long in the tooth. We should update to the latest version. The latest version is backwards compatible with 2.5.1's dfs and mr so this should be painless. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13149) HBase MR is broken on Hadoop 2.5+ Yarn
[
https://issues.apache.org/jira/browse/HBASE-13149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513274#comment-14513274
]
Hudson commented on HBASE-13149:
FAILURE: Integrated in HBase-1.2 #24 (See
[https://builds.apache.org/job/HBase-1.2/24/])
HBASE-13149 HBase MR is broken on Hadoop 2.5+ Yarn (Jerry He) (ndimiduk: rev
39b7a55580206a3b6f6ec5a3f39b1aca2ea50ac0)
* pom.xml
HBase MR is broken on Hadoop 2.5+ Yarn
--
Key: HBASE-13149
URL: https://issues.apache.org/jira/browse/HBASE-13149
Project: HBase
Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0, 0.98.10.1
Reporter: Jerry He
Assignee: Jerry He
Priority: Blocker
Fix For: 2.0.0, 1.1.0, 1.2.0
Attachments: HBASE-13149-0.98.patch, HBASE-13149-master.patch,
jackson-core-asl-compat_report.html, jackson-jaxrs-compat_report.html,
jackson-mapper-asl-compat_report.html, jackson-xc-compat_report.html,
jackson_1.8_to_1.9_compat_report.html
Running the server MR tools is not working on Yarn version 2.5+.
Running org.apache.hadoop.hbase.mapreduce.Export:
{noformat}
Exception in thread main java.lang.NoSuchMethodError:
org.codehaus.jackson.map.ObjectMapper.setSerializationInclusion(Lorg/codehaus/jackson/map/annotate/JsonSerialize$Inclusion;)Lorg/codehaus/jackson/map/ObjectMapper;
at
org.apache.hadoop.yarn.webapp.YarnJacksonJaxbJsonProvider.configObjectMapper(YarnJacksonJaxbJsonProvider.java:59)
at
org.apache.hadoop.yarn.util.timeline.TimelineUtils.clinit(TimelineUtils.java:47)
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:166)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.serviceInit(ResourceMgrDelegate.java:102)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.init(ResourceMgrDelegate.java:96)
at org.apache.hadoop.mapred.YARNRunner.init(YARNRunner.java:112)
at
org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
at org.apache.hadoop.mapreduce.Cluster.init(Cluster.java:82)
at org.apache.hadoop.mapreduce.Cluster.init(Cluster.java:75)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1266)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1262)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
at org.apache.hadoop.mapreduce.Job.connect(Job.java:1261)
at org.apache.hadoop.mapreduce.Job.submit(Job.java:1290)
at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1314)
at org.apache.hadoop.hbase.mapreduce.Export.main(Export.java:189)
{noformat}
The problem seems to be the jackson jar version. HADOOP-10104 updated
jackson version to 1.9.13. YARN-2092 reported a problem as well.
HBase is using jackson 1.8.8. This version of the jar in the classpath seem
to cause the problem.
Should we upgrade to jackson 1.9.13?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13339) Update default Hadoop version to 2.6.0
[ https://issues.apache.org/jira/browse/HBASE-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513282#comment-14513282 ] Lars Hofhansl commented on HBASE-13339: --- I don't recall that we agreed on this. Should be in trunk (2.0) no doubt. There was a longer discussion about 1.1 and I seem to recall that we said we do not want to force a major Hadoop with a minor HBase upgrade and that instead we'd document in the book how build with Hadoop 2.6.0. I'd prefer not to have this in 1.1 and below, unless there is no 1.1 and we'll call that 2.0 (which in the end I also do not like, since it cuts the 1.x cycle short). Quite possible I missed something and we'll rename 1.1 to 2.0 and fork 1.1 from the current 1.0.x, but then we need to do that. :) Update default Hadoop version to 2.6.0 -- Key: HBASE-13339 URL: https://issues.apache.org/jira/browse/HBASE-13339 Project: HBase Issue Type: Bug Components: build Affects Versions: 2.0.0, 1.1.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.1.0, 1.2.0 Attachments: HBASE-13339-v1.patch, HBASE-13339.patch Current default Hadoop version is getting a little long in the tooth. We should update to the latest version. The latest version is backwards compatible with 2.5.1's dfs and mr so this should be painless. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13339) Update default Hadoop version to 2.6.0
[ https://issues.apache.org/jira/browse/HBASE-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513283#comment-14513283 ] Lars Hofhansl commented on HBASE-13339: --- Specifically we cannot release 1.1 out of branch-1 if the latter is the plan. Update default Hadoop version to 2.6.0 -- Key: HBASE-13339 URL: https://issues.apache.org/jira/browse/HBASE-13339 Project: HBase Issue Type: Bug Components: build Affects Versions: 2.0.0, 1.1.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.1.0, 1.2.0 Attachments: HBASE-13339-v1.patch, HBASE-13339.patch Current default Hadoop version is getting a little long in the tooth. We should update to the latest version. The latest version is backwards compatible with 2.5.1's dfs and mr so this should be painless. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13537) Change the admin interface for async operations to return Future.
[ https://issues.apache.org/jira/browse/HBASE-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Srungarapu updated HBASE-13537: Attachment: HBASE-13537_v2.patch Change the admin interface for async operations to return Future. - Key: HBASE-13537 URL: https://issues.apache.org/jira/browse/HBASE-13537 Project: HBase Issue Type: Sub-task Components: proc-v2 Affects Versions: 2.0.0 Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Attachments: HBASE-13537.patch, HBASE-13537.patch, HBASE-13537.patch, HBASE-13537_v2.patch At the moment, the async operations are returning void. This task aims to change the return type to Future and remove the aysnc wrapper methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13259) mmap() based BucketCache IOEngine
[ https://issues.apache.org/jira/browse/HBASE-13259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513177#comment-14513177 ] Nick Dimiduk commented on HBASE-13259: -- Alright. It's too late now for 1.1, but we should be able to get this for 1.2. [~stack] what other tests would you like to see run? I can see about finding some cycles in a couple weeks. mmap() based BucketCache IOEngine - Key: HBASE-13259 URL: https://issues.apache.org/jira/browse/HBASE-13259 Project: HBase Issue Type: New Feature Components: BlockCache Affects Versions: 0.98.10 Reporter: Zee Chen Fix For: 2.0.0, 1.2.0 Attachments: HBASE-13259-v2.patch, HBASE-13259.patch, ioread-1.svg, mmap-0.98-v1.patch, mmap-1.svg, mmap-trunk-v1.patch Of the existing BucketCache IOEngines, FileIOEngine uses pread() to copy data from kernel space to user space. This is a good choice when the total working set size is much bigger than the available RAM and the latency is dominated by IO access. However, when the entire working set is small enough to fit in the RAM, using mmap() (and subsequent memcpy()) to move data from kernel space to user space is faster. I have run some short keyval gets tests and the results indicate a reduction of 2%-7% of kernel CPU on my system, depending on the load. On the gets, the latency histograms from mmap() are identical to those from pread(), but peak throughput is close to 40% higher. This patch modifies ByteByfferArray to allow it to specify a backing file. Example for using this feature: set hbase.bucketcache.ioengine to mmap:/dev/shm/bucketcache.0 in hbase-site.xml. Attached perf measured CPU usage breakdown in flames graph. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13533) section on configuring ~/.m2/settings.xml has no anchor
[ https://issues.apache.org/jira/browse/HBASE-13533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513211#comment-14513211 ] Gabor Liptak commented on HBASE-13533: -- [~ndimiduk] How did you generate the book? (My local build seems to be still broken ...) section on configuring ~/.m2/settings.xml has no anchor --- Key: HBASE-13533 URL: https://issues.apache.org/jira/browse/HBASE-13533 Project: HBase Issue Type: Bug Components: documentation Reporter: Nick Dimiduk Assignee: Gabor Liptak Priority: Trivial Attachments: HBASE-13533.patch From http://hbase.apache.org/book.html#maven.snapshot there's a link to mvn.settings.file that is invalid. I think the intended destination is the example listing at the beginning of 131.1, above. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13260) Bootstrap Tables for fun and profit
[ https://issues.apache.org/jira/browse/HBASE-13260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513220#comment-14513220 ] Matteo Bertozzi commented on HBASE-13260: - code looks good, and there are some nice cleanups in region/wal code. but now that I'm testing it, I'm not sure if we should replace the proc-wal with this. following what stack mentioned, there is too much overhead on the region path compared to the simple wal. I was expecting the performance of the region to be even better then the simple wal because it never had love, no optimization of any kind and similar. but the region looks at least an of magnitude slower then the simple wal on write. keep in mind that with the simple wal it is easy to do optimization on replay, which is where I expect to get more benefit from using it. anyway, taking one step back and without looking too much into performance. the question is, what benefit we have by using the region instead of a simple wal? in theory the only benefit we have is that we can query it with the table interface, but at this point with this patch we can probably wrap the proc-v2 wal in an EmbeddedTable or similar. the other benefit of course is that the code is probably more tested than the proc-wal and we have already features like compression/encryption in. the main disadvantage is that is that the overhead compared to the wal on the write side looks too much, and making optimization on the replay it may not be that simple. I was in favor of replacing the proc-wal with this before testing it, but now i'm no longer sure about it. so, if you can come up with a list of benefit and disadvantages of using the region vs proc-wal it will be nice to make everyone able to decide. (I'm still +1 on including this patch even without having it used as proc-wal replacement, because looks useful anyway, and it has some nice cleanups) Bootstrap Tables for fun and profit Key: HBASE-13260 URL: https://issues.apache.org/jira/browse/HBASE-13260 Project: HBase Issue Type: Bug Reporter: Enis Soztutar Assignee: Enis Soztutar Fix For: 2.0.0, 1.1.0 Attachments: hbase-13260_bench.patch, hbase-13260_prototype.patch Over at the ProcV2 discussions(HBASE-12439) and elsewhere I was mentioning an idea where we may want to use regular old regions to store/persist some data needed for HBase master to operate. We regularly use system tables for storing system data. acl, meta, namespace, quota are some examples. We also store the table state in meta now. Some data is persisted in zk only (replication peers and replication state, etc). We are moving away from zk as a permanent storage. As any self-respecting database does, we should store almost all of our data in HBase itself. However, we have an availability dependency between different kinds of data. For example all system tables need meta to be assigned first. All master operations need ns table to be assigned, etc. For at least two types of data, (1) procedure v2 states, (2) RS groups in HBASE-6721 we cannot depend on meta being assigned since assignment itself will depend on accessing this data. The solution in (1) is to implement a custom WAL format, and custom recover lease and WAL recovery. The solution in (2) is to have the table to store this data, but also cache it in zk for bootrapping initial assignments. For solving both of the above (and possible future use cases if any), I propose we add a boostrap table concept, which is: - A set of predefined tables hosted in a separate dir in HDFS. - A table is only 1 region, not splittable - Not assigned through regular assignment - Hosted only on 1 server (typically master) - Has a dedicated WAL. - A service does WAL recovery + fencing for these tables. This has the benefit of using a region to keep the data, but frees us to re-implement caching and we can use the same WAL / Memstore / Recovery mechanisms that are battle-tested. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13431) Move splitStoreFile to SplitTransaction interface to allow creating both reference files in case required
[ https://issues.apache.org/jira/browse/HBASE-13431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513206#comment-14513206 ] Nick Dimiduk commented on HBASE-13431: -- Where do we stand with this one. Clock is ticking on 1.1? Move splitStoreFile to SplitTransaction interface to allow creating both reference files in case required - Key: HBASE-13431 URL: https://issues.apache.org/jira/browse/HBASE-13431 Project: HBase Issue Type: Improvement Reporter: Rajeshbabu Chintaguntla Assignee: Andrew Purtell Fix For: 2.0.0, 1.1.0 APPROACH #3 at PHOENIX-1734 helps to implement local indexing without much changes in HBase. For split we need one kernel change to allow creating both top and bottom reference files for index column family store files even when the split key not in the storefile key range. The changes helps in this case are 1) pass boolean to HRegionFileSystem#splitStoreFile to allow to skip the storefile key range check. 2) move the splitStoreFile with extra boolean parameter to the new interface introduced at HBASE-12975. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (HBASE-13569) correct errors reported with mvn site
Gabor Liptak created HBASE-13569: Summary: correct errors reported with mvn site Key: HBASE-13569 URL: https://issues.apache.org/jira/browse/HBASE-13569 Project: HBase Issue Type: Bug Reporter: Gabor Liptak Priority: Minor There are a number of Javadoc errors reported when running mvn site. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13149) HBase MR is broken on Hadoop 2.5+ Yarn
[
https://issues.apache.org/jira/browse/HBASE-13149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated HBASE-13149:
-
Resolution: Fixed
Fix Version/s: 1.2.0
Status: Resolved (was: Patch Available)
Per discussions [0], [1], I've pushed this to branch-1.1+.
Thanks [~jinghe]. Mind giving us a nice release note summarizing the reasoning
here?
[0]:
http://mail-archives.apache.org/mod_mbox/hbase-dev/201504.mbox/%3CCA+RK=_C6OJi=y_4xtmhjz2yusbmpd9tvvhnk_p9zmi_cahu...@mail.gmail.com%3E
[1]:
http://mail-archives.apache.org/mod_mbox/hbase-dev/201504.mbox/%3cCA+RK=_CkTUfa3nWPsy2A0PZt07h=1stp72rcazbrw5u0jfd...@mail.gmail.com%3e
HBase MR is broken on Hadoop 2.5+ Yarn
--
Key: HBASE-13149
URL: https://issues.apache.org/jira/browse/HBASE-13149
Project: HBase
Issue Type: Bug
Affects Versions: 1.0.0, 2.0.0, 0.98.10.1
Reporter: Jerry He
Assignee: Jerry He
Priority: Blocker
Fix For: 2.0.0, 1.1.0, 1.2.0
Attachments: HBASE-13149-0.98.patch, HBASE-13149-master.patch,
jackson-core-asl-compat_report.html, jackson-jaxrs-compat_report.html,
jackson-mapper-asl-compat_report.html, jackson-xc-compat_report.html,
jackson_1.8_to_1.9_compat_report.html
Running the server MR tools is not working on Yarn version 2.5+.
Running org.apache.hadoop.hbase.mapreduce.Export:
{noformat}
Exception in thread main java.lang.NoSuchMethodError:
org.codehaus.jackson.map.ObjectMapper.setSerializationInclusion(Lorg/codehaus/jackson/map/annotate/JsonSerialize$Inclusion;)Lorg/codehaus/jackson/map/ObjectMapper;
at
org.apache.hadoop.yarn.webapp.YarnJacksonJaxbJsonProvider.configObjectMapper(YarnJacksonJaxbJsonProvider.java:59)
at
org.apache.hadoop.yarn.util.timeline.TimelineUtils.clinit(TimelineUtils.java:47)
at
org.apache.hadoop.yarn.client.api.impl.YarnClientImpl.serviceInit(YarnClientImpl.java:166)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.serviceInit(ResourceMgrDelegate.java:102)
at
org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at
org.apache.hadoop.mapred.ResourceMgrDelegate.init(ResourceMgrDelegate.java:96)
at org.apache.hadoop.mapred.YARNRunner.init(YARNRunner.java:112)
at
org.apache.hadoop.mapred.YarnClientProtocolProvider.create(YarnClientProtocolProvider.java:34)
at org.apache.hadoop.mapreduce.Cluster.initialize(Cluster.java:95)
at org.apache.hadoop.mapreduce.Cluster.init(Cluster.java:82)
at org.apache.hadoop.mapreduce.Cluster.init(Cluster.java:75)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1266)
at org.apache.hadoop.mapreduce.Job$9.run(Job.java:1262)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:415)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
at org.apache.hadoop.mapreduce.Job.connect(Job.java:1261)
at org.apache.hadoop.mapreduce.Job.submit(Job.java:1290)
at org.apache.hadoop.mapreduce.Job.waitForCompletion(Job.java:1314)
at org.apache.hadoop.hbase.mapreduce.Export.main(Export.java:189)
{noformat}
The problem seems to be the jackson jar version. HADOOP-10104 updated
jackson version to 1.9.13. YARN-2092 reported a problem as well.
HBase is using jackson 1.8.8. This version of the jar in the classpath seem
to cause the problem.
Should we upgrade to jackson 1.9.13?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13339) Update default Hadoop version to 2.6.0
[ https://issues.apache.org/jira/browse/HBASE-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513226#comment-14513226 ] Hudson commented on HBASE-13339: FAILURE: Integrated in HBase-1.1 #430 (See [https://builds.apache.org/job/HBase-1.1/430/]) HBASE-13339 Update default Hadoop version to 2.6.0 (ndimiduk: rev 56761d04e06e1e21a2b3257dd5989ba5e3240468) * pom.xml Update default Hadoop version to 2.6.0 -- Key: HBASE-13339 URL: https://issues.apache.org/jira/browse/HBASE-13339 Project: HBase Issue Type: Bug Components: build Affects Versions: 2.0.0, 1.1.0 Reporter: Elliott Clark Assignee: Elliott Clark Fix For: 2.0.0, 1.1.0, 1.2.0 Attachments: HBASE-13339-v1.patch, HBASE-13339.patch Current default Hadoop version is getting a little long in the tooth. We should update to the latest version. The latest version is backwards compatible with 2.5.1's dfs and mr so this should be painless. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13533) section on configuring ~/.m2/settings.xml has no anchor
[
https://issues.apache.org/jira/browse/HBASE-13533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513212#comment-14513212
]
Nick Dimiduk commented on HBASE-13533:
--
I used {{mvn clean site -DskipTests}}.
What's broken about your build? Mind paste some stack trace? FYI, I used to
have problems building the site, with JDK1.7u20-ish. Updating JDK version to
later 1.7 release solved it.
section on configuring ~/.m2/settings.xml has no anchor
---
Key: HBASE-13533
URL: https://issues.apache.org/jira/browse/HBASE-13533
Project: HBase
Issue Type: Bug
Components: documentation
Reporter: Nick Dimiduk
Assignee: Gabor Liptak
Priority: Trivial
Attachments: HBASE-13533.patch
From http://hbase.apache.org/book.html#maven.snapshot there's a link to
mvn.settings.file that is invalid. I think the intended destination is the
example listing at the beginning of 131.1, above.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13569) correct errors reported with mvn site
[ https://issues.apache.org/jira/browse/HBASE-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Liptak updated HBASE-13569: - Release Note: Correct Javadoc (for Java 8) Status: Patch Available (was: Open) correct errors reported with mvn site - Key: HBASE-13569 URL: https://issues.apache.org/jira/browse/HBASE-13569 Project: HBase Issue Type: Bug Reporter: Gabor Liptak Priority: Minor Attachments: HBASE-13569.patch There are a number of Javadoc errors reported when running mvn site. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13569) correct errors reported with mvn site
[ https://issues.apache.org/jira/browse/HBASE-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gabor Liptak updated HBASE-13569: - Attachment: HBASE-13569.patch correct errors reported with mvn site - Key: HBASE-13569 URL: https://issues.apache.org/jira/browse/HBASE-13569 Project: HBase Issue Type: Bug Reporter: Gabor Liptak Priority: Minor Attachments: HBASE-13569.patch There are a number of Javadoc errors reported when running mvn site. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13563) Add missing table owner to AC tests.
[ https://issues.apache.org/jira/browse/HBASE-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513389#comment-14513389 ] Hudson commented on HBASE-13563: FAILURE: Integrated in HBase-1.2 #26 (See [https://builds.apache.org/job/HBase-1.2/26/]) HBASE-13563 Add missing table owner to AC tests. (ssrungarapu: rev decc9b9c36a803938a35f3a61775df8dbbbd8942) * hbase-server/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessController.java Add missing table owner to AC tests. Key: HBASE-13563 URL: https://issues.apache.org/jira/browse/HBASE-13563 Project: HBase Issue Type: Sub-task Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Priority: Minor Fix For: 2.0.0, 1.0.2, 1.2.0 Attachments: HBASE-13563.patch As per the description. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13563) Add missing table owner to AC tests.
[ https://issues.apache.org/jira/browse/HBASE-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513414#comment-14513414 ] Hudson commented on HBASE-13563: FAILURE: Integrated in HBase-1.0 #883 (See [https://builds.apache.org/job/HBase-1.0/883/]) HBASE-13563 Add missing table owner to AC tests. (ssrungarapu: rev d73b57d7c6a85d563f6373b06e18098d4e864979) * hbase-server/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessController.java Add missing table owner to AC tests. Key: HBASE-13563 URL: https://issues.apache.org/jira/browse/HBASE-13563 Project: HBase Issue Type: Sub-task Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Priority: Minor Fix For: 2.0.0, 1.0.2, 1.2.0 Attachments: HBASE-13563.patch As per the description. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13356) HBase should provide an InputFormat supporting multiple scans in mapreduce jobs over snapshots
[ https://issues.apache.org/jira/browse/HBASE-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mains updated HBASE-13356: - Attachment: HBASE-13356.2.patch Thanks for the review! I believe I've addressed all of the comments and hadoop QA errors in this second patch (it goes through everything in test-patch.sh, at least on my local). Let me know if there's anything else I can fix up. HBase should provide an InputFormat supporting multiple scans in mapreduce jobs over snapshots -- Key: HBASE-13356 URL: https://issues.apache.org/jira/browse/HBASE-13356 Project: HBase Issue Type: New Feature Components: mapreduce Reporter: Andrew Mains Assignee: Andrew Mains Priority: Minor Attachments: HBASE-13356.2.patch, HBASE-13356.patch Currently, HBase supports the pushing of multiple scans to mapreduce jobs over live tables (via MultiTableInputFormat) but only supports a single scan for mapreduce jobs over table snapshots. It would be handy to support multiple scans over snapshots as well, probably through another input format (MultiTableSnapshotInputFormat?). To mimic the functionality present in MultiTableInputFormat, the new input format would likely have to take in the names of all snapshots used in addition to the scans. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13569) correct errors reported with mvn site
[
https://issues.apache.org/jira/browse/HBASE-13569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513390#comment-14513390
]
Hadoop QA commented on HBASE-13569:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12728281/HBASE-13569.patch
against master branch at commit 75507af9f80716a2dac2dd3d1642d70373976915.
ATTACHMENT ID: 12728281
{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:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/13823//console
This message is automatically generated.
correct errors reported with mvn site
-
Key: HBASE-13569
URL: https://issues.apache.org/jira/browse/HBASE-13569
Project: HBase
Issue Type: Bug
Reporter: Gabor Liptak
Priority: Minor
Attachments: HBASE-13569.patch
There are a number of Javadoc errors reported when running mvn site.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13537) Change the admin interface for async operations to return Future.
[ https://issues.apache.org/jira/browse/HBASE-13537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513429#comment-14513429 ] Hudson commented on HBASE-13537: FAILURE: Integrated in HBase-TRUNK #6416 (See [https://builds.apache.org/job/HBase-TRUNK/6416/]) HBASE-13537 Change the admin interface for async operations to return Future. (ssrungarapu: rev 807142024f37a117d2ba8a76a274ce0dc64ba075) * hbase-client/src/main/java/org/apache/hadoop/hbase/client/Admin.java * hbase-client/src/main/java/org/apache/hadoop/hbase/client/HBaseAdmin.java Change the admin interface for async operations to return Future. - Key: HBASE-13537 URL: https://issues.apache.org/jira/browse/HBASE-13537 Project: HBase Issue Type: Sub-task Components: proc-v2 Affects Versions: 2.0.0 Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Fix For: 2.0.0 Attachments: HBASE-13537.patch, HBASE-13537.patch, HBASE-13537.patch, HBASE-13537_v2.patch At the moment, the async operations are returning void. This task aims to change the return type to Future and remove the aysnc wrapper methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13563) Add missing table owner to AC tests.
[ https://issues.apache.org/jira/browse/HBASE-13563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513430#comment-14513430 ] Hudson commented on HBASE-13563: FAILURE: Integrated in HBase-TRUNK #6416 (See [https://builds.apache.org/job/HBase-TRUNK/6416/]) HBASE-13563 Add missing table owner to AC tests. (ssrungarapu: rev 75507af9f80716a2dac2dd3d1642d70373976915) * hbase-server/src/test/java/org/apache/hadoop/hbase/security/access/TestAccessController.java Add missing table owner to AC tests. Key: HBASE-13563 URL: https://issues.apache.org/jira/browse/HBASE-13563 Project: HBase Issue Type: Sub-task Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Priority: Minor Fix For: 2.0.0, 1.0.2, 1.2.0 Attachments: HBASE-13563.patch As per the description. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13570) hbase daemon foreground start command executes output of ulimit
[
https://issues.apache.org/jira/browse/HBASE-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-13570:
Status: Patch Available (was: Open)
hbase daemon foreground start command executes output of ulimit
---
Key: HBASE-13570
URL: https://issues.apache.org/jira/browse/HBASE-13570
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.98.11, 2.0.0, 1.1.0
Reporter: Sean Busbey
Assignee: Sean Busbey
Fix For: 2.0.0, 1.1.0, 0.98.13
Attachments: HBASE-13570.1.patch.txt
typo in foreground_start command.
{code}
`ulimit -a` $HBASE_LOGLOG 21
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13358) Upgrade VisibilityClient API to accept Connection object.
[
https://issues.apache.org/jira/browse/HBASE-13358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513491#comment-14513491
]
Anoop Sam John commented on HBASE-13358:
New APIs introduction looks good to me. Just skimmed the test changes. Looks
ok. Have not verified whether replacement of conf with SUPER_USER-CON/
NORMAL_USER_CON is correct. [~srikanth235] want to review and commit it?
Upgrade VisibilityClient API to accept Connection object.
-
Key: HBASE-13358
URL: https://issues.apache.org/jira/browse/HBASE-13358
Project: HBase
Issue Type: Improvement
Reporter: Srikanth Srungarapu
Assignee: Matt Warhaftig
Priority: Minor
Fix For: 2.0.0
Attachments: HBASE-13358.patch, HBASE-13358_v2.patch
From VisibilityClient class:
{code}
// TODO: Make it so caller passes in a Connection rather than have us do
this expensive
// setup each time. This class only used in test and shell at moment
though.
{code}
Basically, this is the VC's counterpart of HBASE-13171.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (HBASE-13570) hbase daemon foreground start command executes output of ulimit
Sean Busbey created HBASE-13570:
---
Summary: hbase daemon foreground start command executes output of
ulimit
Key: HBASE-13570
URL: https://issues.apache.org/jira/browse/HBASE-13570
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 0.98.11, 2.0.0, 1.1.0
Reporter: Sean Busbey
Assignee: Sean Busbey
Fix For: 2.0.0, 1.1.0, 0.98.13
typo in foreground_start command.
{code}
`ulimit -a` $HBASE_LOGLOG 21
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13568) Make Waiter class a public API.
[
https://issues.apache.org/jira/browse/HBASE-13568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513541#comment-14513541
]
Srikanth Srungarapu commented on HBASE-13568:
-
Second draft for fixing the checkstyle and javadoc errors. I left out the
following checkstyle error.
{code}
while (!(eval = predicate.evaluate())
(remainderWait = mustEnd - System.currentTimeMillis()) 0) {
//
}
{code}
Checkstyle is not liking the inner assignment..I can fix this by changing this
to the following.
{code}
eval = predicate.evaluate();
remainderWait = mustEnd - System.currentTimeMillis();
while(!eval remainderWait 0) {
//
eval = predicate.evaluate();
remainderWait = mustEnd - System.currentTimeMillis();
}
{code}
But first version looks more appealing. Thoughts?
Make Waiter class a public API.
---
Key: HBASE-13568
URL: https://issues.apache.org/jira/browse/HBASE-13568
Project: HBase
Issue Type: Task
Reporter: Srikanth Srungarapu
Assignee: Srikanth Srungarapu
Priority: Minor
Attachments: HBASE-13568.patch, HBASE-13568_v2.patch
During ProcV2 code reviews, it is suggested that Waiter class is useful
enough to make it a public API. This change decomposes the existing Waiter
class into two classes, one for public use and the other exclusively for the
internal testing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13359) Update ACL matrix to include table owner.
[
https://issues.apache.org/jira/browse/HBASE-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513533#comment-14513533
]
Hadoop QA commented on HBASE-13359:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12728292/HBASE-13359_v2.patch
against master branch at commit 75507af9f80716a2dac2dd3d1642d70373976915.
ATTACHMENT ID: 12728292
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.1 2.5.2 2.6.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+|| modifyTable |
superuser\|global(A)\|global\(C)\|NS(A)\|NS\(C)\|TableOwner\|table(A)\|table\(C)
+|| deleteTable |
superuser\|global(A)\|global\(C)\|NS(A)\|NS\(C)\|TableOwner\|table(A)\|table\(C)
+|| truncateTable |
superuser\|global(A)\|global\(C)\|NS(A)\|NS\(C)\|TableOwner\|table(A)\|table\(C)
+|| addColumn |
superuser\|global(A)\|global\(C)\|NS(A)\|NS\(C)\|TableOwner\|table(A)\|table\(C)
+|| modifyColumn |
superuser\|global(A)\|global\(C)\|NS(A)\|NS\(C)\|TableOwner\|table(A)\|table\(C)\|column(A)\|column\(C)
+|| deleteColumn |
superuser\|global(A)\|global\(C)\|NS(A)\|NS\(C)\|TableOwner\|table(A)\|table\(C)\|column(A)\|column\(C)
+|| enableTable |
superuser\|global(A)\|global\(C)\|NS(A)\|NS\(C)\|TableOwner\|table(A)\|table\(C)
+|| disableTable |
superuser\|global(A)\|global\(C)\|NS(A)\|NS\(C)\|TableOwner\|table(A)\|table\(C)
+|| flushTable |
superuser\|global(A)\|global\(C)\|NS(A)\|NS\(C)\|TableOwner\|table(A)\|table\(C)
+|| getTableDescriptors* |
superuser\|global(A)\|global\(C)\|NS(A)\|NS\(C)\|TableOwner\|table(A)\|table\(C)
{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.util.TestHBaseFsck
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/13824//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13824//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/13824//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/13824//console
This message is automatically generated.
Update ACL matrix to include table owner.
-
Key: HBASE-13359
URL: https://issues.apache.org/jira/browse/HBASE-13359
Project: HBase
Issue Type: Bug
Components: documentation
Reporter: Srikanth Srungarapu
Assignee: Srikanth Srungarapu
Priority: Minor
Fix For: 2.0.0
Attachments: HBASE-13359.patch, HBASE-13359_v2.patch
Looks like we allow table owner to truncate and modify table. We should
update ACL matrix to reflect this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-10800) Use CellComparator instead of KVComparator
[ https://issues.apache.org/jira/browse/HBASE-10800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-10800: --- Status: Open (was: Patch Available) Use CellComparator instead of KVComparator -- Key: HBASE-10800 URL: https://issues.apache.org/jira/browse/HBASE-10800 Project: HBase Issue Type: Sub-task Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-10800_1.patch, HBASE-10800_11.patch, HBASE-10800_12.patch, HBASE-10800_13.patch, HBASE-10800_14.patch, HBASE-10800_15.patch, HBASE-10800_16.patch, HBASE-10800_18.patch, HBASE-10800_2.patch, HBASE-10800_23.patch, HBASE-10800_3.patch, HBASE-10800_4.patch, HBASE-10800_4.patch, HBASE-10800_5.patch, HBASE-10800_6.patch, HBASE-10800_7.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10800) Use CellComparator instead of KVComparator
[ https://issues.apache.org/jira/browse/HBASE-10800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-10800: --- Attachment: HBASE-10800_23.patch Trying for QA run. Use CellComparator instead of KVComparator -- Key: HBASE-10800 URL: https://issues.apache.org/jira/browse/HBASE-10800 Project: HBase Issue Type: Sub-task Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-10800_1.patch, HBASE-10800_11.patch, HBASE-10800_12.patch, HBASE-10800_13.patch, HBASE-10800_14.patch, HBASE-10800_15.patch, HBASE-10800_16.patch, HBASE-10800_18.patch, HBASE-10800_2.patch, HBASE-10800_23.patch, HBASE-10800_3.patch, HBASE-10800_4.patch, HBASE-10800_4.patch, HBASE-10800_5.patch, HBASE-10800_6.patch, HBASE-10800_7.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13472) Polish IN_MEMORY table behavior
[ https://issues.apache.org/jira/browse/HBASE-13472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513525#comment-14513525 ] Anoop Sam John commented on HBASE-13472: bq. Consider table quota support with an option for region size limits as % of total heap consumed by regions for a given table. Warn at soft limit. Refuse writes if over hard limit. Ya.. I was thinking about this as a work after the offheaping Jira. When we can have HBase RS with more and more cache, we would need better tuning of the size shares for different tables. So Quotas can help here. We have L1 and L2 cache now (In 2 modes). I was thinking whether we can extend this. We have L1 cache in on heap and L2 in Offheap (BC) and a L3 in BC file mode (SSDs). Out of scope of this Jira. Just noting down here as here we speak about keeping more data in cache. We would need quota control and table level priority control cc [~stack] Polish IN_MEMORY table behavior --- Key: HBASE-13472 URL: https://issues.apache.org/jira/browse/HBASE-13472 Project: HBase Issue Type: Task Reporter: Andrew Purtell For a long time we've been able to support a mode of operation that keeps as much table data as possible in memory, so HBase can be used as an 'in-memory' DB with fully durable WAL and write-behind persistence of table data. However: - There are a set of relevant schema options (IN_MEMORY, CACHE_ON_WRITE, PREFETCH_BLOCKS_ON_OPEN, block encoding), so set up isn't simple. We should have a shortcut that sets all this up in one place. I'm thinking a utility class with static helpers that configure a table descriptor with all of the needed bits. (Other ideas?) - We don't have a safety valve. An in-memory table can become too large, where it falls out of blockcache and performs poorly without warning because it's become too big. Consider table quota support with an option for region size limits as % of total heap consumed by regions for a given table. Warn at soft limit. Refuse writes if over hard limit. Follow on work can investigate options hooking up to offheap work. That's not in scope here. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13356) HBase should provide an InputFormat supporting multiple scans in mapreduce jobs over snapshots
[
https://issues.apache.org/jira/browse/HBASE-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513548#comment-14513548
]
Hadoop QA commented on HBASE-13356:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12728296/HBASE-13356.3.patch
against master branch at commit 75507af9f80716a2dac2dd3d1642d70373976915.
ATTACHMENT ID: 12728296
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 14 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.1 2.5.2 2.6.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.util.TestHBaseFsck
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/13825//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13825//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/13825//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/13825//console
This message is automatically generated.
HBase should provide an InputFormat supporting multiple scans in mapreduce
jobs over snapshots
--
Key: HBASE-13356
URL: https://issues.apache.org/jira/browse/HBASE-13356
Project: HBase
Issue Type: New Feature
Components: mapreduce
Reporter: Andrew Mains
Assignee: Andrew Mains
Priority: Minor
Attachments: HBASE-13356.2.patch, HBASE-13356.3.patch,
HBASE-13356.patch
Currently, HBase supports the pushing of multiple scans to mapreduce jobs
over live tables (via MultiTableInputFormat) but only supports a single scan
for mapreduce jobs over table snapshots. It would be handy to support
multiple scans over snapshots as well, probably through another input format
(MultiTableSnapshotInputFormat?). To mimic the functionality present in
MultiTableInputFormat, the new input format would likely have to take in the
names of all snapshots used in addition to the scans.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13568) Make Waiter class a public API.
[ https://issues.apache.org/jira/browse/HBASE-13568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Srungarapu updated HBASE-13568: Attachment: HBASE-13568_v2.patch Make Waiter class a public API. --- Key: HBASE-13568 URL: https://issues.apache.org/jira/browse/HBASE-13568 Project: HBase Issue Type: Task Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Priority: Minor Attachments: HBASE-13568.patch, HBASE-13568_v2.patch During ProcV2 code reviews, it is suggested that Waiter class is useful enough to make it a public API. This change decomposes the existing Waiter class into two classes, one for public use and the other exclusively for the internal testing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-10800) Use CellComparator instead of KVComparator
[ https://issues.apache.org/jira/browse/HBASE-10800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HBASE-10800: --- Status: Patch Available (was: Open) Use CellComparator instead of KVComparator -- Key: HBASE-10800 URL: https://issues.apache.org/jira/browse/HBASE-10800 Project: HBase Issue Type: Sub-task Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 2.0.0 Attachments: HBASE-10800_1.patch, HBASE-10800_11.patch, HBASE-10800_12.patch, HBASE-10800_13.patch, HBASE-10800_14.patch, HBASE-10800_15.patch, HBASE-10800_16.patch, HBASE-10800_18.patch, HBASE-10800_2.patch, HBASE-10800_23.patch, HBASE-10800_3.patch, HBASE-10800_4.patch, HBASE-10800_4.patch, HBASE-10800_5.patch, HBASE-10800_6.patch, HBASE-10800_7.patch -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13570) hbase daemon foreground start command executes output of ulimit
[
https://issues.apache.org/jira/browse/HBASE-13570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-13570:
Attachment: HBASE-13570.1.patch.txt
trivial patch.
hbase daemon foreground start command executes output of ulimit
---
Key: HBASE-13570
URL: https://issues.apache.org/jira/browse/HBASE-13570
Project: HBase
Issue Type: Bug
Components: scripts
Affects Versions: 2.0.0, 1.1.0, 0.98.11
Reporter: Sean Busbey
Assignee: Sean Busbey
Fix For: 2.0.0, 1.1.0, 0.98.13
Attachments: HBASE-13570.1.patch.txt
typo in foreground_start command.
{code}
`ulimit -a` $HBASE_LOGLOG 21
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HBASE-13359) Update ACL matrix to include table owner.
[
https://issues.apache.org/jira/browse/HBASE-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Srikanth Srungarapu updated HBASE-13359:
Attachment: HBASE-13359_v2.patch
Changed {{Table Owner}} to {{TableOwner}} as rendering is much better for the
latter.
Update ACL matrix to include table owner.
-
Key: HBASE-13359
URL: https://issues.apache.org/jira/browse/HBASE-13359
Project: HBase
Issue Type: Bug
Components: documentation
Reporter: Srikanth Srungarapu
Assignee: Srikanth Srungarapu
Priority: Minor
Attachments: HBASE-13359.patch, HBASE-13359_v2.patch
Looks like we allow table owner to truncate and modify table. We should
update ACL matrix to reflect this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13356) HBase should provide an InputFormat supporting multiple scans in mapreduce jobs over snapshots
[
https://issues.apache.org/jira/browse/HBASE-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513444#comment-14513444
]
Ted Yu commented on HBASE-13356:
{code}
50 @InterfaceAudience.Public
51 @InterfaceStability.Evolving
52 public class MultiTableSnapshotInputFormatImpl {
{code}
Does MultiTableSnapshotInputFormatImpl have to be public ? It can be
LimitedPrivate, right ?
{code}
34 public final class ConfigurationUtil {
{code}
ConfigurationUtil should be annotated with @InterfaceAudience.Public
HBase should provide an InputFormat supporting multiple scans in mapreduce
jobs over snapshots
--
Key: HBASE-13356
URL: https://issues.apache.org/jira/browse/HBASE-13356
Project: HBase
Issue Type: New Feature
Components: mapreduce
Reporter: Andrew Mains
Assignee: Andrew Mains
Priority: Minor
Attachments: HBASE-13356.2.patch, HBASE-13356.patch
Currently, HBase supports the pushing of multiple scans to mapreduce jobs
over live tables (via MultiTableInputFormat) but only supports a single scan
for mapreduce jobs over table snapshots. It would be handy to support
multiple scans over snapshots as well, probably through another input format
(MultiTableSnapshotInputFormat?). To mimic the functionality present in
MultiTableInputFormat, the new input format would likely have to take in the
names of all snapshots used in addition to the scans.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-13554) Update book clarifying API stability guarantees
[ https://issues.apache.org/jira/browse/HBASE-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513447#comment-14513447 ] Misty Stanley-Jones commented on HBASE-13554: - Published. Good to close this? Update book clarifying API stability guarantees --- Key: HBASE-13554 URL: https://issues.apache.org/jira/browse/HBASE-13554 Project: HBase Issue Type: Task Components: documentation Reporter: Josh Elser Assignee: Josh Elser Fix For: 2.0.0 Attachments: HBASE-13554.patch From the Clarifying interface evolution freedom in patch releases [thread|http://mail-archives.apache.org/mod_mbox/hbase-dev/201504.mbox/%3CCA%2BRK%3D_CkTUfa3nWPsy2A0PZt07h%3D1stP72rcazBrw5U0JFdgXA%40mail.gmail.com%3E] on dev@h.a.o Seems we have consensus that HBase uses Semantic Versioning isn't quite correct (or desired) at the moment. Update the documentation to make sure we're not misrepresenting any guarantees to users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13554) Update book clarifying API stability guarantees
[ https://issues.apache.org/jira/browse/HBASE-13554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser updated HBASE-13554: --- Resolution: Fixed Status: Resolved (was: Patch Available) Looks good to me. Thanks [~misty] and [~busbey]! Update book clarifying API stability guarantees --- Key: HBASE-13554 URL: https://issues.apache.org/jira/browse/HBASE-13554 Project: HBase Issue Type: Task Components: documentation Reporter: Josh Elser Assignee: Josh Elser Fix For: 2.0.0 Attachments: HBASE-13554.patch From the Clarifying interface evolution freedom in patch releases [thread|http://mail-archives.apache.org/mod_mbox/hbase-dev/201504.mbox/%3CCA%2BRK%3D_CkTUfa3nWPsy2A0PZt07h%3D1stP72rcazBrw5U0JFdgXA%40mail.gmail.com%3E] on dev@h.a.o Seems we have consensus that HBase uses Semantic Versioning isn't quite correct (or desired) at the moment. Update the documentation to make sure we're not misrepresenting any guarantees to users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13359) Update ACL matrix to include table owner.
[ https://issues.apache.org/jira/browse/HBASE-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513458#comment-14513458 ] Misty Stanley-Jones commented on HBASE-13359: - Still +1 from me Update ACL matrix to include table owner. - Key: HBASE-13359 URL: https://issues.apache.org/jira/browse/HBASE-13359 Project: HBase Issue Type: Bug Components: documentation Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Priority: Minor Attachments: HBASE-13359.patch, HBASE-13359_v2.patch Looks like we allow table owner to truncate and modify table. We should update ACL matrix to reflect this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13356) HBase should provide an InputFormat supporting multiple scans in mapreduce jobs over snapshots
[ https://issues.apache.org/jira/browse/HBASE-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513456#comment-14513456 ] Andrew Mains commented on HBASE-13356: -- Does MultiTableSnapshotInputFormatImpl have to be public ? It can be LimitedPrivate, right ? Probably so, yeah (I was going off of TableSnapshotInputFormatImpl, which is Public, but LimitedPrivate makes more sense for an implementation class). ConfigurationUtil should be annotated with @InterfaceAudience.Public Done. HBase should provide an InputFormat supporting multiple scans in mapreduce jobs over snapshots -- Key: HBASE-13356 URL: https://issues.apache.org/jira/browse/HBASE-13356 Project: HBase Issue Type: New Feature Components: mapreduce Reporter: Andrew Mains Assignee: Andrew Mains Priority: Minor Attachments: HBASE-13356.2.patch, HBASE-13356.3.patch, HBASE-13356.patch Currently, HBase supports the pushing of multiple scans to mapreduce jobs over live tables (via MultiTableInputFormat) but only supports a single scan for mapreduce jobs over table snapshots. It would be handy to support multiple scans over snapshots as well, probably through another input format (MultiTableSnapshotInputFormat?). To mimic the functionality present in MultiTableInputFormat, the new input format would likely have to take in the names of all snapshots used in addition to the scans. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13356) HBase should provide an InputFormat supporting multiple scans in mapreduce jobs over snapshots
[ https://issues.apache.org/jira/browse/HBASE-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Mains updated HBASE-13356: - Attachment: HBASE-13356.3.patch HBase should provide an InputFormat supporting multiple scans in mapreduce jobs over snapshots -- Key: HBASE-13356 URL: https://issues.apache.org/jira/browse/HBASE-13356 Project: HBase Issue Type: New Feature Components: mapreduce Reporter: Andrew Mains Assignee: Andrew Mains Priority: Minor Attachments: HBASE-13356.2.patch, HBASE-13356.3.patch, HBASE-13356.patch Currently, HBase supports the pushing of multiple scans to mapreduce jobs over live tables (via MultiTableInputFormat) but only supports a single scan for mapreduce jobs over table snapshots. It would be handy to support multiple scans over snapshots as well, probably through another input format (MultiTableSnapshotInputFormat?). To mimic the functionality present in MultiTableInputFormat, the new input format would likely have to take in the names of all snapshots used in addition to the scans. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HBASE-13359) Update ACL matrix to include table owner.
[ https://issues.apache.org/jira/browse/HBASE-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Srikanth Srungarapu updated HBASE-13359: Resolution: Fixed Fix Version/s: 2.0.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) Pushed to master branch. Thanks Misty for the review. Update ACL matrix to include table owner. - Key: HBASE-13359 URL: https://issues.apache.org/jira/browse/HBASE-13359 Project: HBase Issue Type: Bug Components: documentation Reporter: Srikanth Srungarapu Assignee: Srikanth Srungarapu Priority: Minor Fix For: 2.0.0 Attachments: HBASE-13359.patch, HBASE-13359_v2.patch Looks like we allow table owner to truncate and modify table. We should update ACL matrix to reflect this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-12221) Port TestFromClientSide to hbase-it
[ https://issues.apache.org/jira/browse/HBASE-12221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513468#comment-14513468 ] Enis Soztutar commented on HBASE-12221: --- [~dimaspivak] any update on this one? Having a client side test as IT will definitely help release candidate testing a lot. Now that we have 0.98, 1.0 and 1.1 active release lines where the clients should be interoperable, we are lacking an easy way to verify. I think we don't need every test in TestFromClientSide. We can start from the simplest tests, then expand on the base. Port TestFromClientSide to hbase-it --- Key: HBASE-12221 URL: https://issues.apache.org/jira/browse/HBASE-12221 Project: HBase Issue Type: New Feature Affects Versions: 1.0.0, 2.0.0, 0.98.7 Reporter: Dima Spivak Assignee: Dima Spivak org.apache.hadoop.hbase.client.TestFromClientSide touches a lot of the HBase Java API and would be a nice integration test to have for anyone looking to verify end-to-end functionality. I'd like to turn it into an integration test and have it live in hbase-it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (HBASE-13356) HBase should provide an InputFormat supporting multiple scans in mapreduce jobs over snapshots
[
https://issues.apache.org/jira/browse/HBASE-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14513474#comment-14513474
]
Hadoop QA commented on HBASE-13356:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12728280/HBASE-13356.2.patch
against master branch at commit 75507af9f80716a2dac2dd3d1642d70373976915.
ATTACHMENT ID: 12728280
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 14 new
or modified tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.1 2.5.2 2.6.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.util.TestHBaseFsck
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/13822//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/13822//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/13822//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/13822//console
This message is automatically generated.
HBase should provide an InputFormat supporting multiple scans in mapreduce
jobs over snapshots
--
Key: HBASE-13356
URL: https://issues.apache.org/jira/browse/HBASE-13356
Project: HBase
Issue Type: New Feature
Components: mapreduce
Reporter: Andrew Mains
Assignee: Andrew Mains
Priority: Minor
Attachments: HBASE-13356.2.patch, HBASE-13356.3.patch,
HBASE-13356.patch
Currently, HBase supports the pushing of multiple scans to mapreduce jobs
over live tables (via MultiTableInputFormat) but only supports a single scan
for mapreduce jobs over table snapshots. It would be handy to support
multiple scans over snapshots as well, probably through another input format
(MultiTableSnapshotInputFormat?). To mimic the functionality present in
MultiTableInputFormat, the new input format would likely have to take in the
names of all snapshots used in addition to the scans.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
