+1
Thanks Zhankun for all of your hard work on this release.
> On Sep 20, 2019, at 5:34 AM, epa...@apache.org wrote:
>
>
>
> +1 (binding)
>
> Thanks Zhankun for all of your hard work on this release.
>
> I downloaded and built the source and ran it on an insecure multi-node pseudo
> cluste
For more details, see
https://builds.apache.org/job/hadoop-qbt-branch2-java7-linux-x86/453/
No changes
-1 overall
The following subsystems voted -1:
compile findbugs hadolint mvninstall mvnsite pathlen unit xml
The following subsystems voted -1 but
were configured to be filtered/ignor
Jinglun created HDFS-14867:
--
Summary: RBF: RouterRpcServer.getListing() returns wrong owner,
group and permission.
Key: HDFS-14867
URL: https://issues.apache.org/jira/browse/HDFS-14867
Project: Hadoop HDFS
Thanks Steve.
Idea is not to shade all artifacts.
Instead maintain one artifact ( hadoop-thirdparty) which have all such
dependencies ( com.google.* may be), add this artifact as dependency in
hadoop modules. Use shaded classes directly in the code of hadoop modules
instead of shading at package
On Sun, Sep 22, 2019 at 3:22 PM Vinayakumar B
wrote:
>Protobuf provides Wire compatibility between releases.. but not
> guarantees the source compatibility in generated sources. There will be a
> problem in compatibility if anyone uses generated protobuf message outside
> of Hadoop modules. W
Nanda kumar created HDDS-2164:
-
Summary: om.db.checkpoints is getting filling up fast
Key: HDDS-2164
URL: https://issues.apache.org/jira/browse/HDDS-2164
Project: Hadoop Distributed Data Store
Is
Protobuf provides Wire compatibility between releases.. but not
guarantees the source compatibility in generated sources. There will be a
problem in compatibility if anyone uses generated protobuf message outside
of Hadoop modules. Which ideally shouldn't be as generated sources are not
public A
Quick question, being lazy here, lots of JIRA updates on HADOOP-13363 over the
years not helping either.
Does anyone know what this upgrade will mean w.r.t compatibility for the Hadoop
releases themselves? Remember that trunk is still 3.x.
Thanks
+Vinod
> On Sep 21, 2019, at 9:55 AM, Vinayakum
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
th
[
https://issues.apache.org/jira/browse/HDDS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar reopened HDDS-2020:
---
Reopening for ozone-0.4.1 branch.
> Remove mTLS from Ozone GRPC
> ---
>
>
[
https://issues.apache.org/jira/browse/HDDS-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar reopened HDDS-2001:
---
> Update Ratis version to 0.4.0
> -
>
> Key: HDDS-2001
>
Thanks all who helped to verify and vote 3.2.1 release! I am concluding the
vote for 3.2.1 RC0.
Summary of votes for hadoop-3.2.1-RC0:
7 binding +1s, from:
--
Sunil Govindan, Brahma Reddy Battula, Steve Loughran, Elek, Marton, Weiwei
Yang, Naganarasimha Garla, Rohith Sharm
Inline comments
On Thu, 19 Sep 2019 at 11:51, Rohith Sharma K S
wrote:
> Thanks Brahma for voting and bringing this to my attention!
>
> On Thu, 19 Sep 2019 at 11:28, Brahma Reddy Battula
> wrote:
>
>> RohithThanks for driving the release
>>
>> +1 (Binding).
>>
>> --Built from the source
>> --I
13 matches
Mail list logo