[
https://issues.apache.org/jira/browse/BIGTOP-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463895#comment-13463895
]
Roman Shaposhnik commented on BIGTOP-714:
-----------------------------------------
bq. I was under the impression that 0.23.3 is the latest Hadoop release (being
released 2 months after 2.0.1-alpha).
Welcome to the world of Hadoop version numbers -- where releases and versions
don't make much sense (still). Now, to be fair the whole renumbering to 1.X and
2.X happened precisely because of the mess that uses to be.
Anyway, at the moment the only two actively developed Hadoop branches are
Hadoop 1.X and Hadoop 2.X everything else is maintained for particular use
cases with release managers essentially cherry-picking fixes ONLY for the
things they care about. IOW, all of the bug fixes, etc. go either into 1.X or
2.X. You're really way better off using one of those branches. Don't be
confused by the release numbers since in Hadoop (actually all of the Apache) it
is not uncommon to have releases running in parallel.
bq. Can you build the latest hadoop with bigtop, not 2.0.0-alpha as in bigtop
trunk?
The latest released Hadoop in 2.X seriues is Hadoop 2.0.1-aplha and we are
likely to target 2.0.2-alpha for the Bigtop 0.5.0. I believe neither has this
issue. If you're interested in Hadoop 1.X then the latest release one is Hadoop
1.0.3 which also doesn't seem to suffer from this problem.
Once again: anybody who cares about 0.23.X should take it up with the current
release manager (Bobby Evans from Yahoo!)
> HDFS Fuse build broken for 0.23.3
> ---------------------------------
>
> Key: BIGTOP-714
> URL: https://issues.apache.org/jira/browse/BIGTOP-714
> Project: Bigtop
> Issue Type: Improvement
> Components: General
> Affects Versions: 0.5.0
> Reporter: Erich Schubert
>
> The -Pfuse flag seems to have been removed upstream. The future support of
> fuse-dfs seems to be unclear (it was voted as unmaintained and removed from
> the default build and there are maintained alternatives, others say it still
> is alive ...)
> It probably still lives in the contrib folder, and can be built by ant.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
