[
https://issues.apache.org/jira/browse/HADOOP-1920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528682
]
Hadoop QA commented on HADOOP-1920:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12366149/sh.patch
against trunk revision r577010.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests -1. The patch failed contrib unit tests.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/788/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/788/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/788/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/788/console
This message is automatically generated.
> [hbase] Wrapper scripts broken when hadoop in one location and hbase in
> another
> -------------------------------------------------------------------------------
>
> Key: HADOOP-1920
> URL: https://issues.apache.org/jira/browse/HADOOP-1920
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: stack
> Assignee: stack
> Priority: Minor
> Fix For: 0.15.0
>
> Attachments: sh.patch
>
>
> In-house, hadoop is installed into one location and the desire is that hbase
> can be installed elsewhere as its own distinct component that can be revved
> independent of base hadoop. The wrapper scripts give the impression that this
> is currently possible with support for separate HADOOP_HOME/HBASE_HOME,
> HADOOP_CONF_DIR/HBASE_CONF_DIR, etc, only trying it this evening the scripts
> fail; key settings are not being forwarded out to remote regionservers on the
> cluster.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
