Thanks Vinod and Akira..
I assume we will have at least a committer review of any force-push. Say,
if the commit history already has x, y, z, now we need to force push with
x', we'd better not torget y and z, and if there is conflict putting in y
and z after x', the conflict is better reviewed.
M
good enough for handling them IMO.
>
> Thanks
> +Vinod
>
> > On Jan 14, 2016, at 8:07 PM, Yongjun Zhang wrote:
> >
> > I assume we will have at least a committer review of any force-push. Say,
> > if the commit history already has x, y, z, now we need to force pu
Hi Junping,
Thanks a lot for leading the effort on 2.6.4.
We were discussing in HDFS-9629, and have agreement on adding an additional
step in the release process to update the year in the webui footer. See
https://issues.apache.org/jira/browse/HDFS-9629?focusedCommentId=15130043&page=com.atlassi
HI,
Would like to bring this to your attention:
Per the discussion in HDFS-9629, we think it'd be helpful to add an extra
step in the release process when creating RC. The purpose of this extra
step is to update the release year in Web UI footer.
I have created https://issues.apache.org/jira/bro
Thanks Junping again for working on this release.
+1 (binding),
- Downloaded source tarball and binary tarball
- Verified signature and checksum for both source and binary tarballs
- Compiled and built a single node cluster
- Run HDFS shell commands to create files
- Run distcp job between this n
Thanks Junping and Allen.
It'd be nice to have HDFS-9629 but I'm ok with option 2, given the fact
that the issue is not critical (and will be addressed in all future
releases), and the concern Allen raised.
Best,
--Yongjun
On Wed, Feb 10, 2016 at 8:37 AM, Allen Wittenauer wrote:
>
> > On Feb
Thanks Andrew for initiating the effort!
+1 on pushing 3.x with extended alpha cycle, and continuing the more stable
2.x releases.
--Yongjun
On Thu, Feb 18, 2016 at 5:58 PM, Andrew Wang
wrote:
> Hi Kai,
>
> Sure, I'm open to it. It's a new major release, so we're allowed to make
> these kinds
That's nice, thanks Andrew and Allen.
--Yongjun
On Thu, Mar 3, 2016 at 9:11 PM, Andrew Wang
wrote:
> Hi all,
>
> With the inclusion of HADOOP-12651 going back to branch-2.8, CHANGES.txt
> and release notes are now generated by Yetus. I've gone ahead and deleted
> the manually updated CHANGES.tx
HI,
I saw this couple of times lately: A jenkins test job have finished running
test, updating the corresponding jira and sending out email notification.
However, the test report is not ready at the the link sent in the email,
and the console link shows that the job is still running.
I wonder if
Thanks Arpit for throwing this discussion as part of HADOOP-10888
investigation! It's a good guess of Arpit's about possible missing
/etc/hosts entry.
Please feel free to comment in HADOOP-10888 so information can be
centralized there.
Best regards,
--Yongjun
On Wed, Jul 23, 2014 at 9:07 PM,
1" row for IPv4 but I don't see
it in the "::1" row for IPv6 in /etc/hosts file. I wonder if adding
"asf900" as an entry to "::1" row would make it work. The method stuck
at is java.net.Inet4AddressImpl.getLocalHostName (IPv4) though.
>
Thanks.
--Yongj
.ygridcore.net*asf900*
It would be good to look at all hosts here
https://builds.apache.org/computer/H/
(https://builds.apache.org/computer/H0/,
https://builds.apache.org/computer/H01/ ...)
because they might have same issue.
Thanks a lot.
--Yongjun
On Thu, Jul 24, 2014 at 8:22 PM, Yongjun Zhang
Thanks Ted, I just filed https://issues.apache.org/jira/browse/INFRA-8097.
--Yongjun
On Thu, Jul 24, 2014 at 10:23 PM, Ted Yu wrote:
> Have you filed an INFRA JIRA so that infrastructure team can fix this ?
>
> Cheers
>
>
> On Thu, Jul 24, 2014 at 9:18 PM, Yongjun Zhang
&
gt; be critical.
>
> Cheers
>
>
> On Fri, Jul 25, 2014 at 6:46 AM, Yongjun Zhang
> wrote:
>
> > Thanks Ted, I just filed
> https://issues.apache.org/jira/browse/INFRA-8097.
> >
> > --Yongjun
> >
> >
> > On Thu, Jul 24, 2014 at 10:23 PM, T
, Jul 26, 2014 at 7:59 AM, Giridharan Kesavan <
gkesa...@hortonworks.com> wrote:
> ASF infra folks doesn't support jenkins build infrastructure. You should
> send an email to bui...@apache.org
>
>
> -giri
>
>
> On Fri, Jul 25, 2014 at 7:13 PM, Yongjun Zhang
>
+1 (non-binding), pending the document issue Akira found out
+ downloaded src tarball and did build
+ deployed two pseudo-distributed clusters
+ ran some sample mapreduce job on one cluster
+ ran basic distcp test between the two clusters
Thanks.
--Yongjun
On Sun, Aug 10, 2014 at 9:35 PM, Akira
Hi,
I just noticed that the recent jenkin test report doesn't include link to
test result, however, the email notice does show the failed tests:
E.g.
https://builds.apache.org/job/PreCommit-HDFS-Build/7846//
Example old job report that has the link:
https://builds.apache.org/job/PreCommit-HDFS
hadoop.hdfs.TestDFSClientRetries.testGetFileChecksum
1: org.apache.hadoop.hdfs.TestDFSClientRetries.testNamenodeRestart
[yzhang@localhost jenkinsftf]$
On Thu, Aug 28, 2014 at 8:04 PM, Yongjun Zhang wrote:
> Hi,
>
> I just noticed that the recent jenkin test report doesn't include link to
>
in dev-support directory ?
>
> Thanks
>
> On Aug 30, 2014, at 11:10 PM, Yongjun Zhang wrote:
>
> > Hi,
> >
> > I developed a tool to detect flaky tests of hadoop jenkins test jobs, on
> > top of the initial work Todd Lipcon did. We find it quite useful, an
Congratulations Andrew and all, a great milestone! Thanks Andrew for
driving it!
--Yongjun
On Tue, Dec 19, 2017 at 9:10 AM, Jonathan Kelly
wrote:
> Thanks, Andrew!
>
> On Mon, Dec 18, 2017 at 4:54 PM Andrew Wang
> wrote:
>
> > Thanks for the spot, I just pushed a correct tag. I can't delete th
Hi All,
>
We have released Apache Hadoop 3.0.2 in April of this year [1]. Since then,
there are quite some commits done to branch-3.0. To further improve the
quality of release, we plan to do 3.0.3 release now. The focus of 3.0.3
will be fixing blockers (3), critical bugs (17) and bug fixes (~130)
-Eric Payne
>
>
>
>
>
> On Monday, May 7, 2018, 12:09:00 AM CDT, Yongjun Zhang <
> yjzhan...@apache.org> wrote:
>
>
>
>
>
> Hi All,
>
> >
> We have released Apache Hadoop 3.0.2 in April of this year [1]. Since then,
> there are quite some
>> downstream projects can't pick it up (after the fact that HBase is one of
>> the most important projects around Hadoop).
>>
>> On Mon, May 7, 2018 at 1:19 PM, Yongjun Zhang
>> wrote:
>>
>> > Hi Eric,
>> >
>> > Thanks for the
please
> refer to CHANGES [2] and RELEASENOTES [3].
> - For download, please got to download page[4]
>
> Thank you all for contributing to the Apache Hadoop 2.9.1.
>
>
> Last, thanks Yongjun Zhang, Junping Du, Andrew Wang and Chris Douglas for
> your help and support.
>
&
in 3.0.3 release. This is a fix that
> will enable HBase to use Hadoop 3.0.x in the production line.
>
> thanks
> Vrushali
>
>
> On Tue, May 8, 2018 at 10:24 AM, Yongjun Zhang
> wrote:
>
>> Thanks Wei-Chiu and Haibo for the feedback!
>>
>> Good thing is th
> too early.
>
> Echoing Eric Payne, I think we should wait to cut the branch until we are
> actually creating the RC to vote on (i.e. on May 29 or 30 if the vote is to
> be on May 30).
>
> Eric
>
>
>
> On Wed, May 23, 2018 at 4:11 PM, Yongjun Zhang
> wrote:
>
Hi All,
I will be working on cutting the 3.0.3 branch and trying a build today.
Thanks.
--Yongjun
On Wed, May 23, 2018 at 3:31 PM, Yongjun Zhang wrote:
> Thanks Eric. Sounds good. I may try to see if I can do the branching/RC
> sooner.
>
> --Yongjun
>
>
> On Wed, Ma
HI,
I did build before cut branch and hit some issues, have not got to the
bottom, will cut branch after the build issues are resolved.
Thanks.
--Yongjun
On Sat, May 26, 2018 at 1:46 PM, Yongjun Zhang wrote:
> Hi All,
>
> I will be working on cutting the 3.0.3 branch and trying a bu
ndrew Wang,
Eddy Xu who helped when I tried to solve the build issues.
At this point, please be aware of the existence of branch-3.0, branch-3.0.3.
Best,
--Yongjun
On Sat, May 26, 2018 at 11:52 PM, Yongjun Zhang wrote:
> HI,
>
> I did build before cut branch and hit some issues, h
Sorry, forgot to mention Junping Du, who also helped me a lot. Many thanks
Junping!
Thanks.
--Yongjun
On Wed, May 30, 2018 at 11:49 AM, Yongjun Zhang
wrote:
> Hi,
>
> The build issues are all solved, and I have cut the 3.0.3 branch and close
> to get a build out. Since it'
rther. Sorry for the inconvenience.
--Yongjun
On Wed, May 30, 2018 at 11:49 AM, Yongjun Zhang
wrote:
> Hi,
>
> The build issues are all solved, and I have cut the 3.0.3 branch and close
> to get a build out. Since it's taking me a bit more time (I expect to send
> vote invitation
Greetings all,
I've created the first release candidate (RC0) for Apache Hadoop
3.0.3. This is our next maintenance release to follow up 3.0.2. It includes
about 249
important fixes and improvements, among which there are 8 blockers. See
https://issues.apache.org/jira/issues/?filter=12343997
The
ems to be private. I can't see the
>> blocker list.
>> https://issues.apache.org/jira/issues/?filter=12343997
>>
>> Meanwhile , I will be working on testing the release.
>>
>> Thanks
>> Shashi
>> On 6/1/18, 11:18 AM, "Yongjun Zhang" wr
>> https://issues.apache.org/jira/issues/?filter=12343997
>
> Even after logging in, I am not able to see any jiras.
> It says "The requested filter doesn't exist or is private."
>
> On Fri, Jun 1, 2018 at 10:41 AM, Yongjun Zhang
> wrote:
>
>> Thank
jobs work as expected
> - Verified that user weights work as expected
> - Verified that FairOrderingPolicy in a CS queue will evenly assign
> resources
> - Verified running yarn shell application runs as expected
>
>
>
>
>
>
>
> On Friday, June 1, 2018,
t; - basic sanity check of NN, RM UI
> >
> > Thanks,
> > Ajay
> >
> > On 6/2/18, 12:45 AM, "Shashikant Banerjee" <
> sbaner...@hortonworks.com>
> > wrote:
> >
> > Hi Yongjun,
> >
Hi Gabor,
I got the git tag in, it's release-3.0.3-RC0. Would you please give it a
try?
It should correspond to
commit 37fd7d752db73d984dc31e0cdfd590d252f5e075
Author: Yongjun Zhang
Date: Wed May 30 00:07:33 2018 -0700
Update version to 3.0.3 to prepare for 3.0.3 release
T
bu Asanuma
> wrote:
>
>> Sorry, I forgot to write my vote in the last message.
>>
>> +1 (non-binding)
>>
>> Regards,
>> Takanobu
>>
>> > -Original Message-
>> > From: Takanobu Asanuma [mailto:tasan...@yahoo-corp.jp]
>> >
Thank you all very much for the testing, feedback and discussion!
I was able to build outside docker, by following the steps Nanda described,
I saw the same problem; then I tried 3.0.2 released a while back, it has
the same issue.
As Allen pointed out, it seems the steps to build site are not cor
BTW, thanks Allen and Steve for discussing and suggestion about the site
build problem I hit earlier, I did the following step
mvn install -DskipTests
before doing the steps Nanda listed helped to solve the problems.
--Yongjun
On Thu, Jun 7, 2018 at 6:15 PM, Yongjun Zhang wrote:
> Th
Hello,
PMC votes are needed for release, can I get some help from PMCs?
Really appreciate it!
--Yongjun
On Thu, Jun 7, 2018 at 6:15 PM, Yongjun Zhang wrote:
> Thank you all very much for the testing, feedback and discussion!
>
> I was able to build outside docker, by following
istributed HDFS with KMS
>>- Ran basic hdfs commands with encryption
>>- Sanity checked webui and logs
>>
>>
>>
>> -Xiao
>>
>> On Fri, Jun 8, 2018 at 10:34 AM, Brahma Reddy Battula <
>> brahmareddy.batt...@hotmail.com> wrote:
>>
Verified that various queue config properties for CS are refreshable
> - Verified streaming jobs work as expected
> - Verified that user weights work as expected
> - Verified that FairOrderingPolicy in a CS queue will evenly assign
> resources
> - Verified running yarn shell applicatio
can resume the build with the
> command
> [ERROR] mvn -rf :hadoop-shim
>
> Not seeing the artifact published here as well.
> https://mvnrepository.com/artifact/org.apache.hadoop/hadoop-project
>
> On Tue, Jun 12, 2018 at 6:44 PM, Yongjun Zhang
> wrote:
>
>> Thank
today and now 2.9.1 is pushed to the mvn repo.
>>
>> You can double check it. I suspect sometimes Nexus may fail to notify
>> user when this is unexpected failures.
>>
>>
>>
>>
>>
>> Bests,
>>
>> Sammi
>>
>> *From:* Yongj
--Yongjun
On Mon, Jul 9, 2018 at 2:08 PM, Jonathan Eagles wrote:
> Thank you, Yongjun Zhang for resolving this issue for me. I have verified
> the 3.0.3 build is now working for me for tez to specify as a hadoop
> dependency.
>
> As for release procedure, can someone comment o
hadoop.apache.org/releases.html page.
>
> I just did it, FYI: https://svn.apache.org/viewvc?view=revision&revision=
> 1837967
>
> Thanks
> +Vinod
>
>
> On May 31, 2018, at 10:48 PM, Yongjun Zhang wrote:
>
> Greetings all,
>
> I've created the first re
Great work guys.
Wonder if we can elaborate what's impact of not having #2 fixed, and why #2
is not needed for the feature to complete?
2. Need to fix automatic failover with ZKFC. Currently it does not doesn't
know about ObserverNodes trying to convert them to SBNs.
Thanks.
--Yongjun
On Wed, D
insert calls back into the call queue. That's
> > completely unacceptable. A buggy or malicious client can easily cause
> > livelock in the IPC layer with handlers only looping on calls that never
> > satisfy the condition. Why is this not implemented via
> RetriableExcepti
Hi Sangjin,
Thanks a lot for your work here.
My +1 (binding).
- Downloaded both binary and src tarballs
- Verified md5 checksum and signature for both
- Build from source tarball
- Deployed 2 pseudo clusters, one with the released tarball and the other
with what I built from source, and did the
Thanks Andrew much for the work here!
+1 (binding).
- Downloaded both binary and src tarballs
- Verified md5 checksum and signature for both
- Built from source tarball
- Deployed 2 pseudo clusters, one with the released tarball and the other
with what I built from source, and did the following
Hi,
I saw quite a few jenkins test failure for patches uploaded to jira,
For example,
https://builds.apache.org/job/PreCommit-HADOOP-Build/12347/console
apache-yetus-2971eff/yetus-project/pom.xml
Modes: Sentinel MultiJDK Jenkins Robot Docker ResetRepo UnitTests
Processing: HADOOP-14407
HA
Regards,
> Akira
>
> On 2017/05/17 18:38, Yongjun Zhang wrote:
>
>> Hi,
>>
>> I saw quite a few jenkins test failure for patches uploaded to jira,
>>
>> For example,
>> https://builds.apache.org/job/PreCommit-HADOOP-Build/12347/console
>>
>&g
Thanks Arun for the info and reminder.
Hi Alejandro,
HADOOP-10895 is a blocker in the list Arun sent out and it's currently
owned by you. I wonder whether you will have time to work on. If not, would
you mind reassigning it to me and I will spend time on it?
Thanks.
--Yongjun
On Tue, Oct 14,
Hi,
I posted a patch to hadoop-10895 couple of days back. Wonder if anyone
could help doing a review?
Thanks a lot.
--Yongjun
On Sun, Oct 19, 2014 at 11:35 AM, Yongjun Zhang wrote:
> Thanks Arun for the info and reminder.
>
> Hi Alejandro,
>
> HADOOP-10895 is a blocker in the
Thanks Arun for leading the 2.6 release effort.
+1 (non-binding)
- Downloaded rc1 source and did build
- Created two single-node clusters running 2.6
- Ran sample mapreduce job
- Ran distcp between two clusters
--Yongjun
On Thu, Nov 13, 2014 at 3:08 PM, Arun C Murthy wrote:
> Folks,
>
> I've
Hi,
One issue to report here, any help would be greatly appreciated!
I noticed that multiple patch submissions to
https://issues.apache.org/jira/browse/HADOOP-11293
did not trigger jenkins test run.
Thanks Chris Nauroth for the help to trigger one manually for me:
https://builds.apache.org/job/
d problems with that for me a few months back. If you break it
> up per-project, it should work just fine.
>
> -Ray
>
>
> On Fri, Nov 14, 2014 at 1:49 PM, Ted Yu wrote:
>
> > Adding builds@apache
> >
> > On Fri, Nov 14, 2014 at 1:34 PM, Yongjun Zhang
> &g
For all's info, confirmed what Ray stated, indeed it's the reason!
Thanks.
--Yongjun
On Fri, Nov 14, 2014 at 2:40 PM, Yongjun Zhang wrote:
> Many thanks Ray, good to know!
>
> --Yongjun
>
> On Fri, Nov 14, 2014 at 2:03 PM, Ray Chiang wrote:
>
>> Your patch
Hi Suresh,
I did review HDFS-6833 and the patch Shinichi provided a while back. It's
not really directly related to replication factor. The problem reported
there is, DirectoryScanner tries to register with NN blocks already
scheduled to be deleted as regular blocks, due to the delay in block
remo
eady done so, I suggest filing a jira for this.
> >
> > Chris Nauroth
> > Hortonworks
> > http://hortonworks.com/
> >
> >
> > On Sat, Nov 15, 2014 at 8:19 AM, Yongjun Zhang
> > wrote:
> >
> > > For all's info, confirmed what Ra
o, I suggest filing a jira for this.
> > >
> > > Chris Nauroth
> > > Hortonworks
> > > http://hortonworks.com/
> > >
> > >
> > > On Sat, Nov 15, 2014 at 8:19 AM, Yongjun Zhang
> > > wrote:
> > >
> >
Hi,
When I look at patches uploaded to jiras, from time to time I notice that
different revisions of the patch is uploaded with the same patch file name,
some time for quite a few times. It's confusing which is which.
I'd suggest that as a guideline, we do the following when uploading a patch:
tagging the
> commit with the same revision number —but that 's just a personal choice
>
>
>
> On 21 November 2014 at 19:10, Ted Yu wrote:
>
> > bq. include a revision number in the patch file name
> >
> > +1
> >
> > On Fri, Nov 21, 2014 at
gt; commit with the same revision number —but that 's just a personal choice
> >
> >
> >
> > On 21 November 2014 at 19:10, Ted Yu wrote:
> >
> > > bq. include a revision number in the patch file name
> > >
> > > +1
> > >
> &g
Thanks all for the feedback. To summarize (and I have a suggestion at the
end of this email), there are two scenarios:
1. A change that span multiple *bigger* projects. r.g. hadoop, hbase.
2. A change that span multiple *sub* projects* within hadoop, e.g.,
common, hdfs, yarn
For 1, it's
m/umbrant/dotfiles/blob/master/bin/fetch-patch
>
> On Tue, Nov 25, 2014 at 5:44 PM, Harsh J wrote:
>
> > For the same filename, you can observe also that the JIRA colors the
> > latest one to be different than the older ones automatically - this is
> > what I rely on
> > > +1.The "different color for newest patch" doesn't work very well if you
> > > are color blind, so I do appreciate a revision number in the name.
> > >
> > > From: Yongjun Zhang
> > > To: common-dev@hadoop.apache.org
> > > Sent:
lits is the way to do this... There are also
> some patches that are completely mechanical and don't really require the
> involvement of YARN / HDFS committer, even if they change that project.
> For example, fixing a misspelling in the name of a hadoop-common API.
>
> Colin
>
>
> > https://wiki.apache.org/hadoop/HowToContribute#Naming_your_patch
> >
> > On Dec 2, 2014, at 10:01 AM, Tsuyoshi OZAWA
> > wrote:
> >
> > >> .[branchName.].patch*
> > >
> > > +1 for this format. Thanks for starting the discussion, Y
ble to edit after a relogin.
>
> On Wed, Dec 3, 2014 at 1:43 AM, Yongjun Zhang wrote:
> > Thanks Allen, Andrew and Tsuyoshi.
> >
> > My wiki user name is YongjunZhang, I will appreciate it very much if
> > someone can give me the permission to edit the wiki pages. Thanks
Hi,
I wonder if anyone can help on resolving HADOOP-11320
<https://issues.apache.org/jira/browse/HADOOP-11320> to increase timeout
for jenkins test of crossing-subproject patches?
Thanks a lot,
--Yongjun
On Tue, Dec 2, 2014 at 10:10 AM, Yongjun Zhang wrote:
> Hi,
>
> Thank
Many thanks to Ted Yu, Steve Loughran and Andrew Wang for replying in the
jira and Steve/Andrew for making the related changes!
--Yongjun
On Thu, Dec 11, 2014 at 12:41 PM, Yongjun Zhang wrote:
> Hi,
>
> I wonder if anyone can help on resolving HADOOP-11320
> <https://issues.
Sorry my bad, I named Andrew Wang for Andrew Bayer in my last mail, both of
them helped anyways:-) So thanks to all for the help on this matter!
--Yongjun
On Thu, Dec 11, 2014 at 3:38 PM, Yongjun Zhang wrote:
> Many thanks to Ted Yu, Steve Loughran and Andrew Wang for replying in the
>
On Thu, Dec 4, 2014 at 10:18 AM, Tsuyoshi OZAWA
> wrote:
> >
> > Thanks Yongjun and Harsh for updating Wiki!
> >
> > Thanks,
> > - Tsuyoshi
> >
> > On Thu, Dec 4, 2014 at 9:43 AM, Yongjun Zhang
> wrote:
> > > Thanks Harsh, I just made a
ick them in a dir
> > specific
> > > > to that JIRA; I can work out what the highest number is and increment
> > it
> > > by
> > > > one for creating a new one...yet retain the whole patch history
> > locally.
> > > >
> > > > I
Hi,
When creating jira, there is a "Labels" entry where we could label the jira
as supportability. It would help to do this, so we could possibly give
priority to fix them for better supportability, especially for those JIRAs
that tend to be small but very high-impact for end users.
The types of
Thanks Kihwal for bringing this up.
Seems related to:
https://issues.apache.org/jira/browse/HADOOP-11084
Hi Andrew/Arpit/Colin/Steve, you guys worked on this jira before, any
insight about the issue Kihwal described?
Thanks.
--Yongjun
On Thu, Feb 5, 2015 at 9:49 AM, Kihwal Lee
wrote:
> I a
Hi,
Thanks for working on 2.7 release.
Currently the fallback from KerberosAuthenticator to
PseudoAuthenticator is enabled by default in a hardcoded way. HAOOP-10895
changes the default and requires applications (such as oozie) to set a
config property or call an API to enable the fallback.
Thi
Thanks Andrew for the proposal.
+1, and I will be happy to help.
--Yongjun
On Mon, Mar 2, 2015 at 3:19 PM, Andrew Wang
wrote:
> Hi devs,
>
> It's been a year and a half since 2.x went GA, and I think we're about due
> for a 3.x release.
> Notably, there are two incompatible changes I'd like
Thanks all.
There is an open issue HDFS-6962 (ACLs inheritance conflicts with
umaskmode), for which the incompatibility appears to make it not suitable
for 2.x and it's targetted 3.0, please see:
https://issues.apache.org/jira/browse/HDFS-6962?focusedCommentId=14335418&page=com.atlassian.jira.plu
Hi,
I found that changing CHANGES.txt when committing a jira is error prone
because of the different sections in the file, and sometimes we forget
about changing this file.
After all, git log would indicate the history of a branch. I wonder if we
could switch to a new method:
1. When committing,
Thanks Sean, that'd be even better!
--Yongjun
On Fri, Mar 13, 2015 at 3:01 PM, Sean Busbey wrote:
> So long as you include the issue number, you can automate pulling the type
> from jira directly instead of putting it in the message.
>
> On Fri, Mar 13, 2015 at 4:49 PM, Yongj
3:01 PM, Sean Busbey wrote:
>
> > So long as you include the issue number, you can automate pulling the
> type
> > from jira directly instead of putting it in the message.
> >
> > On Fri, Mar 13, 2015 at 4:49 PM, Yongjun Zhang
> > wrote:
> >
> > >
low quality of our notes…) Anyway, here’s what I’ve been
> building/using as changes.txt and release notes:
>
> https://github.com/aw-altiscale/hadoop-release-metadata
>
> I try to update these every day. :)
>
> On Mar 13, 2015, at 4:07 PM, Yongjun Zhang wrote:
>
> > T
CHANGES.txt from JIRA and/or git as part of making a
> > release. Or just dropping it altogether. Keeping it under version
> > control creates lot of false conflicts whenever submitting a patch and
> > generally makes committing minor changes unpleasant.
> >
> > Colin
&g
t;> smartishd) "no identification of what type of commit it was without
> hooking
> >> into JIRA anyway." This would be in the format of the commit message
> >>>
> >>> Either way I think would be an improvement.
> >>> Thanks for your i
Great idea Allen, big +1!
Thanks.
--Yongjun
On Thu, Mar 19, 2015 at 11:06 AM, Tsuyoshi Ozawa wrote:
> Hi Allen,
>
> Thank you for the great suggestion. Let's do this!
>
> Thanks,
> - Tsuyoshi
>
> On Fri, Mar 20, 2015 at 2:34 AM, Allen Wittenauer
> wrote:
> >
> > Hi folks,
> >
> > Ther
Thanks Allen a lot for organizing the Haoop Bug Bash, very happy to see
many folks by face!
Wish you all a nice weekend!
--Yongjun
On Tue, May 5, 2015 at 9:31 PM, Allen Wittenauer wrote:
>
> On May 5, 2015, at 8:10 PM, Allen Wittenauer wrote:
>
> > * We’ll be closing registrat
Hi,
We touched this topic before but it was put on hold. I'd like to bring it
to our attention again.
>From time to time we saw changes that work fine in trunk but not branch-2,
and we don't catch the issue in a timely manner. The difference between
trunk and branch-2 is sufficient to justify per
us help on quality.
Thanks.
--Yongjun
On Mon, Jun 15, 2015 at 7:21 AM, Allen Wittenauer wrote:
>
> On Jun 14, 2015, at 1:00 PM, Yongjun Zhang wrote:
>
> > From time to time we saw changes that work fine in trunk but not
> branch-2,
> > and we don't catch the issue in
Yongjun Zhang created HADOOP-12604:
--
Summary: Exception may be swallowed in KMSClientProvider
Key: HADOOP-12604
URL: https://issues.apache.org/jira/browse/HADOOP-12604
Project: Hadoop Common
Yongjun Zhang created HADOOP-10250:
--
Summary: VersionUtil returns wrong value when comparing two
versions
Key: HADOOP-10250
URL: https://issues.apache.org/jira/browse/HADOOP-10250
Project: Hadoop
Yongjun Zhang created HADOOP-10293:
--
Summary: Though symlink is disabled by default, related code
interprets path to be link incorrectly
Key: HADOOP-10293
URL: https://issues.apache.org/jira/browse/HADOOP-10293
Yongjun Zhang created HADOOP-10294:
--
Summary: Using backtick "`" as delimiter for parsing file path
disallows "`" in file path name
Key: HADOOP-10294
URL: https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/HADOOP-10293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yongjun Zhang resolved HADOOP-10293.
Resolution: Fixed
See commit log for
Addendum patch for HADOOP-9652 to fix performance
Yongjun Zhang created HADOOP-10543:
--
Summary: RemoteException's unwrapRemoteException method failed for
PathIOException
Key: HADOOP-10543
URL: https://issues.apache.org/jira/browse/HADOOP-
[
https://issues.apache.org/jira/browse/HADOOP-10510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yongjun Zhang resolved HADOOP-10510.
Resolution: Duplicate
I'm marking this as a duplicate per [~andrew.wang]'s c
Yongjun Zhang created HADOOP-10872:
--
Summary: org.apache.hadoop.fs.shell.TestPathData failed
intermittently with "Mkdirs failed to create d1"
Key: HADOOP-10872
URL: https://issues.apache.org/jira/bro
Yongjun Zhang created HADOOP-10888:
--
Summary: org.apache.hadoop.ipc.TestIPC.testRetryProxy failed often
with timeout
Key: HADOOP-10888
URL: https://issues.apache.org/jira/browse/HADOOP-10888
Project
1 - 100 of 140 matches
Mail list logo
