[
https://issues.apache.org/jira/browse/HBASE-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14086687#comment-14086687
]
Hadoop QA commented on HBASE-6275:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12534363/HBASE-6275.patch
against trunk revision .
ATTACHMENT ID: 12534363
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/10303//console
This message is automatically generated.
> Add conditional Hadoop properties assignment
> --------------------------------------------
>
> Key: HBASE-6275
> URL: https://issues.apache.org/jira/browse/HBASE-6275
> Project: HBase
> Issue Type: Improvement
> Components: Client, master, regionserver
> Affects Versions: 0.95.2
> Reporter: Lars George
> Assignee: Lars George
> Priority: Minor
> Labels: beginner
> Attachments: HBASE-6275.patch
>
>
> See https://issues.apache.org/jira/browse/HBASE-3639, we should use
> VersionInfo to put the proper one in, yet only one of them. Currently we
> always get this message when you start a daemon or the shell:
> {noformat}2012-06-25 16:13:44,819 WARN org.apache.hadoop.conf.Configuration:
> fs.default.name is deprecated. Instead, use fs.defaultFS{noformat}
> As well as this subsequently sporting the same issue:
> {noformat}2012-06-25 16:13:44,819 WARN org.apache.hadoop.conf.Configuration:
> mapred.task.id is deprecated. Instead, use mapreduce.task.attempt.id{noformat}
> And the shell does:
> {noformat}12/06/25 16:05:26 WARN conf.Configuration: hadoop.native.lib is
> deprecated. Instead, use io.native.lib.available{noformat}
> Talking to Stack he suggest:
> {quote}We should make a little function under util to do it because it will be
> reused in a bunch of places (in daemons, shell, out in scripts, etc).{quote}
--
This message was sent by Atlassian JIRA
(v6.2#6252)