hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-16183) Use latest Yetus to support ozone specific build process
Date Tue, 02 Apr 2019 13:50:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-16183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16807773#comment-16807773

Sean Busbey commented on HADOOP-16183:

bq. As far I understand it's not forbidden to use any snapshot version but it shouldn't be
publish for wider audience.

so long as "wider audience" means folks outside of the community defined by the dev@ mailing
list of a given project, we're in agreement. The entire Hadoop project is not on that mailing
list, so it should not be our regular practice to rely on a non-released version.

bq. In fact Hadoop used unreleased (or even forked) yetus multiple times. (You can check the
config history: https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/jobConfigHistory/showDiffFiles?timestamp1=2018-07-10_14-47-51&timestamp2=2018-09-01_21-39-22)

AFAICT someone who is in both the Yetus and Hadoop communities was helpful enough to make
sure that various fixes worked for our project. If you're attempting to see if the change
in yetus actually does what you want and you're subscribed to dev@yetus, you are welcome to
use individual builds to verify things as well. The proposed change here would move Hadoop
to rely on a non-released version continuously. Our use of yetus is a black box to most of
the Hadoop community, and I don't want folks new to it that need to ask questions of the yetus
community to show up on non-released artifacts.

bq. But I respect your opinion, I will ask for a release on the yetus-dev list.


BTW. Wouldn't be better to store the hadoop personality in the hadoop repository? According
to your comment we need a release from an other project (yetus) to change anything in the
build definition/personality. (cc Allen Wittenauer)

I don't have an opinion on how that personality is maintained since I don't put work into
maintaining it.

> Use latest Yetus to support ozone specific build process
> --------------------------------------------------------
>                 Key: HADOOP-16183
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16183
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Elek, Marton
>            Assignee: Elek, Marton
>            Priority: Major
> In YETUS-816 the hadoop personality is improved to better support ozone specific changes.
> Unfortunately the hadoop personality is part of the Yetus project and not the Hadoop
project: we need a new yetus release or switch to an unreleased version.
> In this patch I propose to use the latest commit from yetus (but use that fixed commit
instead updating all the time). 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message