You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-dev@hadoop.apache.org by "Elek, Marton" <el...@apache.org> on 2019/09/23 10:33:45 UTC
Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk
source tree [discussion -> lazy vote]
> Do you see a Submarine like split-also-into-a-TLP for Ozone? If not
now, sometime further down the line?
Good question, and I don't know what is the best answer right now. It's
definitely an option, But Submarine move hasn't been finished, so it's
not yet possible to learn form the experiences (which can be a usefull
input for the decision).
I think it's a bigger/more important question and I would prefer to
start a new thread about it.
> If so, why not do both at the same time?
That's an easier question: I think the repo separation is an easier
step, with immediate benefits, therefore I would prefer to do it as soon
as possible.
Moving to a separated TLP may take months (discussion, vote, proposal,
board approval, etc.). While this code organization step can be done
easily after the 0.4.1 Ozone release (which is very close, I hope).
As it should be done anyway (with or without separated TLP) I propose to
do it after the next Ozone release (in the next 1-2 weeks).
As the overall feedback was positive (in fact many of the answers were
simple +1 votes) I don't think the thread should be repeated under
[VOTE] subject. Therefore I call it for a lazy consensus. If you have
any objections (against doing the repo separation now or doing it at
all) please express in the next 3 days...
Thanks a lot,
Marton
On 9/22/19 4:02 PM, Vinod Kumar Vavilapalli wrote:
> Looks to me that the advantages of this additional step are only incremental given that you've already decoupled releases and dependencies.
>
> Do you see a Submarine like split-also-into-a-TLP for Ozone? If not now, sometime further down the line? If so, why not do both at the same time? I felt the same way with Submarine, but couldn't follow up in time.
>
> Thanks
> +Vinod
>
>> On Sep 18, 2019, at 4:04 AM, Wangda Tan <wh...@gmail.com> wrote:
>>
>> +1 (binding).
>>
>> From my experiences of Submarine project, I think moving to a separate repo
>> helps.
>>
>> - Wangda
>>
>> On Tue, Sep 17, 2019 at 11:41 AM Subru Krishnan <su...@apache.org> wrote:
>>
>>> +1 (binding).
>>>
>>> IIUC, there will not be an Ozone module in trunk anymore as that was my
>>> only concern from the original discussion thread? IMHO, this should be the
>>> default approach for new modules.
>>>
>>> On Tue, Sep 17, 2019 at 9:58 AM Salvatore LaMendola (BLOOMBERG/ 731 LEX) <
>>> slamendola2@bloomberg.net> wrote:
>>>
>>>> +1
>>>>
>>>> From: elek@apache.org At: 09/17/19 05:48:32To:
>>> hdfs-dev@hadoop.apache.org,
>>>> mapreduce-dev@hadoop.apache.org, common-dev@hadoop.apache.org,
>>>> yarn-dev@hadoop.apache.org
>>>> Subject: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk
>>>> source tree
>>>>
>>>>
>>>> TLDR; I propose to move Ozone related code out from Hadoop trunk and
>>>> store it in a separated *Hadoop* git repository apache/hadoop-ozone.git
>>>>
>>>>
>>>> When Ozone was adopted as a new Hadoop subproject it was proposed[1] to
>>>> be part of the source tree but with separated release cadence, mainly
>>>> because it had the hadoop-trunk/SNAPSHOT as compile time dependency.
>>>>
>>>> During the last Ozone releases this dependency is removed to provide
>>>> more stable releases. Instead of using the latest trunk/SNAPSHOT build
>>>> from Hadoop, Ozone uses the latest stable Hadoop (3.2.0 as of now).
>>>>
>>>> As we have no more strict dependency between Hadoop trunk SNAPSHOT and
>>>> Ozone trunk I propose to separate the two code base from each other with
>>>> creating a new Hadoop git repository (apache/hadoop-ozone.git):
>>>>
>>>> With moving Ozone to a separated git repository:
>>>>
>>>> * It would be easier to contribute and understand the build (as of now
>>>> we always need `-f pom.ozone.xml` as a Maven parameter)
>>>> * It would be possible to adjust build process without breaking
>>>> Hadoop/Ozone builds.
>>>> * It would be possible to use different Readme/.asf.yaml/github
>>>> template for the Hadoop Ozone and core Hadoop. (For example the current
>>>> github template [2] has a link to the contribution guideline [3]. Ozone
>>>> has an extended version [4] from this guideline with additional
>>>> information.)
>>>> * Testing would be more safe as it won't be possible to change core
>>>> Hadoop and Hadoop Ozone in the same patch.
>>>> * It would be easier to cut branches for Hadoop releases (based on the
>>>> original consensus, Ozone should be removed from all the release
>>>> branches after creating relase branches from trunk)
>>>>
>>>>
>>>> What do you think?
>>>>
>>>> Thanks,
>>>> Marton
>>>>
>>>> [1]:
>>>>
>>>>
>>> https://lists.apache.org/thread.html/c85e5263dcc0ca1d13cbbe3bcfb53236784a39111b8
>>>> c353f60582eb4@%3Chdfs-dev.hadoop.apache.org%3E
>>>> [2]:
>>>>
>>>>
>>> https://github.com/apache/hadoop/blob/trunk/.github/pull_request_template.md
>>>> [3]:
>>> https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
>>>> [4]:
>>>>
>>>>
>>> https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute+to+Ozone
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
>>>> For additional commands, e-mail: common-dev-help@hadoop.apache.org
>>>>
>>>>
>>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
> For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk
source tree [discussion -> lazy vote]
Posted by "Elek, Marton" <el...@apache.org>.
Sure. Will do it that way.
Thanks the feedback.
Marton
On 10/12/19 7:27 PM, Vinod Kumar Vavilapalli wrote:
> On Mon, Sep 23, 2019 at 4:02 PM Elek, Marton <el...@apache.org> wrote:
>
>> As the overall feedback was positive (in fact many of the answers were
>> simple +1 votes) I don't think the thread should be repeated under
>> [VOTE] subject. Therefore I call it for a lazy consensus.
>>
>
> Let's please not do this in the future.
>
> These are large enough changes that we'd like to get formal votes both for
> immediate visibility (VOTE threads are more in your face) as well as for
> record-keeping in posterity.
>
> Thanks
> +Vinod
>
---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-dev-help@hadoop.apache.org
Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk
source tree [discussion -> lazy vote]
Posted by "Elek, Marton" <el...@apache.org>.
Sure. Will do it that way.
Thanks the feedback.
Marton
On 10/12/19 7:27 PM, Vinod Kumar Vavilapalli wrote:
> On Mon, Sep 23, 2019 at 4:02 PM Elek, Marton <el...@apache.org> wrote:
>
>> As the overall feedback was positive (in fact many of the answers were
>> simple +1 votes) I don't think the thread should be repeated under
>> [VOTE] subject. Therefore I call it for a lazy consensus.
>>
>
> Let's please not do this in the future.
>
> These are large enough changes that we'd like to get formal votes both for
> immediate visibility (VOTE threads are more in your face) as well as for
> record-keeping in posterity.
>
> Thanks
> +Vinod
>
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org
Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk
source tree [discussion -> lazy vote]
Posted by "Elek, Marton" <el...@apache.org>.
Sure. Will do it that way.
Thanks the feedback.
Marton
On 10/12/19 7:27 PM, Vinod Kumar Vavilapalli wrote:
> On Mon, Sep 23, 2019 at 4:02 PM Elek, Marton <el...@apache.org> wrote:
>
>> As the overall feedback was positive (in fact many of the answers were
>> simple +1 votes) I don't think the thread should be repeated under
>> [VOTE] subject. Therefore I call it for a lazy consensus.
>>
>
> Let's please not do this in the future.
>
> These are large enough changes that we'd like to get formal votes both for
> immediate visibility (VOTE threads are more in your face) as well as for
> record-keeping in posterity.
>
> Thanks
> +Vinod
>
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org
Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk
source tree [discussion -> lazy vote]
Posted by "Elek, Marton" <el...@apache.org>.
Sure. Will do it that way.
Thanks the feedback.
Marton
On 10/12/19 7:27 PM, Vinod Kumar Vavilapalli wrote:
> On Mon, Sep 23, 2019 at 4:02 PM Elek, Marton <el...@apache.org> wrote:
>
>> As the overall feedback was positive (in fact many of the answers were
>> simple +1 votes) I don't think the thread should be repeated under
>> [VOTE] subject. Therefore I call it for a lazy consensus.
>>
>
> Let's please not do this in the future.
>
> These are large enough changes that we'd like to get formal votes both for
> immediate visibility (VOTE threads are more in your face) as well as for
> record-keeping in posterity.
>
> Thanks
> +Vinod
>
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org
Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk
source tree [discussion -> lazy vote]
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
On Mon, Sep 23, 2019 at 4:02 PM Elek, Marton <el...@apache.org> wrote:
> As the overall feedback was positive (in fact many of the answers were
> simple +1 votes) I don't think the thread should be repeated under
> [VOTE] subject. Therefore I call it for a lazy consensus.
>
Let's please not do this in the future.
These are large enough changes that we'd like to get formal votes both for
immediate visibility (VOTE threads are more in your face) as well as for
record-keeping in posterity.
Thanks
+Vinod
Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk
source tree [discussion -> lazy vote]
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
On Mon, Sep 23, 2019 at 4:02 PM Elek, Marton <el...@apache.org> wrote:
> As the overall feedback was positive (in fact many of the answers were
> simple +1 votes) I don't think the thread should be repeated under
> [VOTE] subject. Therefore I call it for a lazy consensus.
>
Let's please not do this in the future.
These are large enough changes that we'd like to get formal votes both for
immediate visibility (VOTE threads are more in your face) as well as for
record-keeping in posterity.
Thanks
+Vinod
Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk
source tree [discussion -> lazy vote]
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
On Mon, Sep 23, 2019 at 4:02 PM Elek, Marton <el...@apache.org> wrote:
> As the overall feedback was positive (in fact many of the answers were
> simple +1 votes) I don't think the thread should be repeated under
> [VOTE] subject. Therefore I call it for a lazy consensus.
>
Let's please not do this in the future.
These are large enough changes that we'd like to get formal votes both for
immediate visibility (VOTE threads are more in your face) as well as for
record-keeping in posterity.
Thanks
+Vinod
Re: [DISCUSS] Separate Hadoop Core trunk and Hadoop Ozone trunk
source tree [discussion -> lazy vote]
Posted by Vinod Kumar Vavilapalli <vi...@apache.org>.
On Mon, Sep 23, 2019 at 4:02 PM Elek, Marton <el...@apache.org> wrote:
> As the overall feedback was positive (in fact many of the answers were
> simple +1 votes) I don't think the thread should be repeated under
> [VOTE] subject. Therefore I call it for a lazy consensus.
>
Let's please not do this in the future.
These are large enough changes that we'd like to get formal votes both for
immediate visibility (VOTE threads are more in your face) as well as for
record-keeping in posterity.
Thanks
+Vinod