[
https://issues.apache.org/jira/browse/HBASE-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408028#comment-13408028
]
Zhihong Ted Yu commented on HBASE-6275:
---------------------------------------
bq. do we want to support three different version of Hadoop
I think we should be prepared to.
bq. then using the oldest want work
I guess you meant "won't work"
We actually know the hadoop version HBase is using (hadoop jar file in the
classpath). If we support multiple hadoop versions (1.0, 0.23 and 2.0, 3.0 to
come), we can consider utilizing the effective hadoop version at runtime.
> 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.96.0
> Reporter: Lars George
> Assignee: Lars George
> Priority: Minor
> Fix For: 0.96.0
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
