Owen O'Malley created YARN-11162:
Summary: Set the zk acl for nodes created by ZKConfigurationStore.
Key: YARN-11162
URL: https://issues.apache.org/jira/browse/YARN-11162
Project: Hadoop YARN
I'm very unhappy with this direction. In particular, I don't think git is a
good place for distribution of binary artifacts. Furthermore, the PMC
shouldn't be releasing anything without a release vote.
I'd propose that we make a third party module that contains the *source* of
the pom files to
Since you don't have any Apache Members, I'll join to provide Apache
oversight.
.. Owen
On Fri, Sep 6, 2019 at 1:38 PM Owen O'Malley wrote:
> +1 for moving to a new project.
>
> On Sat, Aug 31, 2019 at 10:19 PM Wangda Tan wrote:
>
>> Hi all,
>>
>> As we discu
+1 for moving to a new project.
On Sat, Aug 31, 2019 at 10:19 PM Wangda Tan wrote:
> Hi all,
>
> As we discussed in the previous thread [1],
>
> I just moved the spin-off proposal to CWIKI and completed all TODO parts.
>
>
>
As we discussed in hdfs-dev@hadoop, I did a force push to Hadoop's trunk to
replace the Ozone merge with a rebase.
That means that you'll need to rebase your branches.
.. Owen
This discussion seems to have died down coming closer consensus without a
resolution.
I'd like to propose the following compromise:
* HDSL become a subproject of Hadoop.
* HDSL will release separately from Hadoop. Hadoop releases will not
contain HDSL and vice versa.
* HDSL will get its own jira
Hi Joep,
On Tue, Mar 6, 2018 at 6:50 PM, J. Rottinghuis
wrote:
Obviously when people do want to use Ozone, then having it in the same repo
> is easier. The flipside is that, separate top-level project in the same
> repo or not, it adds to the Hadoop releases.
>
Apache
On Thu, Mar 1, 2018 at 11:03 PM, Andrew Wang
wrote:
Owen mentioned making a Hadoop subproject; we'd have to
> hash out what exactly this means (I assume a separate repo still managed by
> the Hadoop project), but I think we could make this work if it's more
> attractive
I think it would be good to get this in sooner rather than later, but I
have some thoughts.
1. It is hard to tell what has changed. git rebase -i tells me the
branch has 722 commits. The rebase failed with a conflict. It would really
help if you rebased to current trunk.
2. I think