[ 
https://issues.apache.org/jira/browse/BIGTOP-714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463584#comment-13463584
 ] 

Erich Schubert commented on BIGTOP-714:
---------------------------------------

I was under the impression that 0.23.3 is the latest Hadoop release (being 
released 2 months after 2.0.1-alpha). In fact, the 2.0.0-alpha release notes 
identify that release as 0.23.1:

http://hadoop.apache.org/docs/r2.0.0-alpha/hadoop-project-dist/hadoop-common/releasenotes.html

So if this is 0.23.1, shouldn't 0.23.3 be newer, just not yet rebranded as 
2.0.2-alpha (or 2.0.1-beta?). And in SVN, they all seem to go with 
3.0.0-SNAPSHOT or so already... Versionitis, as pushed by IOS/Chrome/Firefox I 
guess. There is an internal version number, and a marketing version number. 
This is at least he impression I had.

The apache web site somewhere also says:

.bq 0.23.X - simmilar to 2.X.X but missing NN HA.

I do not need NN HA, as I currently have only three nodes.

Anyway, if I recall correctly, I had the same issue when trying to build Hadoop 
"trunk", that -Pfuse was removed. So I belive this was a decision done at 
upstream Hadoop, and that's why I filed this with BIGTOP.

Can you build the latest hadoop with bigtop, not 2.0.0-alpha as in bigtop trunk?
                
> 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

Reply via email to