Genmao Yu created HADOOP-14999:
--
Summary: AliyunOSS: provide block-based output stream to support
large file (> 5GB)
Key: HADOOP-14999
URL: https://issues.apache.org/jira/browse/HADOOP-14999
Project:
Hi Junping,
> In the mean time, branch-2.9 should be reserved for next 2.9 point
release (2.9.1) and branch-2 should be reserved for next minor release
(2.10.0 or whatever name it is). Thoughts?
Yup, That is the current plan. We've updated mvn versions in branch-2 to
point to 2.10.0-SNAPSHOT.
Hi Junping,
We are planning to cut branch-2.9.0 on Thursday as there are couple of
non-blocking bug fixes coming in which we hope to get in tomorrow. Hope
that answers your question.
Thanks,
Subru
On Tue, Oct 31, 2017 at 2:35 PM, 俊平堵 wrote:
> Hi Arun/Subru,
> Thanks
Hi Arun/Subru,
Thanks for updating on 2.9.0 release progress. A quick question here:
are we planning to release from branch-2.9 directly?
I doubt this as it seems against our current branch release practice (
https://wiki.apache.org/hadoop/HowToRelease#Branching). To get rid of any
https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+3+release+status+
updates
2017-10-31
Lots of progress towards GA, we look on track for cutting RC0 this week. I
ran the versions script to check the branch matches up with JIRA and fixed
things up, and also checked that the changelog and
Hi Junping / Wangda,
We just ran jdiff on branch-2.9.
I have copied the output here : http://home.apache.org/~asuresh/2.9.0-jdiff/
We are going thru it but it would be great if you guys can please take a
look and let us know if you spot anything amiss.
Thanks
-Arun
On Mon, Oct 30, 2017 at 4:52
Hello folks
We just cut branch-2.9 since all the critical/blocker issues are now
resolved.
We plan to perform some sanity checks for the rest of the week and cut
branch-2.9.0 and push out an RC0 by the end of the week.
Kindly refrain from committing to branch-2.9 without giving us a heads up.
[
https://issues.apache.org/jira/browse/HADOOP-14555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang resolved HADOOP-14555.
--
Resolution: Duplicate
Fix Version/s: (was: 3.0.0)
> document how to run wasb tests
[
https://issues.apache.org/jira/browse/HADOOP-14555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Wang reopened HADOOP-14555:
--
> document how to run wasb tests in azure docs site/testing.md
>
Robert Kanter created HADOOP-14998:
--
Summary: Make AuthenticationFilter @Public
Key: HADOOP-14998
URL: https://issues.apache.org/jira/browse/HADOOP-14998
Project: Hadoop Common
Issue Type:
Done!
-Akira
On 2017/11/01 1:56, Arpit Agarwal wrote:
Can you please grant me write access too?
Thanks.
On 10/30/17, 11:01 PM, "Akira Ajisaka" wrote:
Done. Welcome!
-Akira
On 2017/10/28 3:26, Hanisha Koneru wrote:
> Hi,
>
>
Thank you, Akira.
-Hanisha
On 10/30/17, 11:01 PM, "Akira Ajisaka" wrote:
>Done. Welcome!
>
>-Akira
>
>On 2017/10/28 3:26, Hanisha Koneru wrote:
>> Hi,
>>
>> Can I please get access to the Confluence Hadoop Wiki. My confluence id is
>> “hanishakoneru”.
>>
>>
New revision...
I have incorporated additions from Mike and added a [DEFAULT] tag to those
items that should be considered for Secure by Default settings.
I am hoping that we can close down on the actual lists shortly and move to
discussing the meta points on how/when to require the completion of
Thanks for the examples, Mike.
I think some of those should actually just be added to the checklist in
other places as they are best practices.
Which raises an interesting point that some of those items can be enabled
by default and maybe indicating so throughout the list makes sense.
Then we
Done. Welcome!
-Akira
On 2017/10/28 3:26, Hanisha Koneru wrote:
Hi,
Can I please get access to the Confluence Hadoop Wiki. My confluence id is
“hanishakoneru”.
Thanks,
Hanisha
-
To unsubscribe, e-mail:
15 matches
Mail list logo