Thanks for taking care of this Sid.
Agree that using jira fix versions would be easier as a way to generate the
changes. It would require some proper handling by the committer. For
example, if something is committed to trunk(3.0.0) and branch-2(2.0.5) it
would have fixedVersion 2.0.5, if later it
I went ahead and committed a couple of changes to trunk and branch-2 to fix
the MR CHANGES.txt mess. Alexandro, I believe there's a couple of jiras
where you were waiting for CHANGES.txt fixes before merging to branch-2.
Not sure about past discussions, but can we re-visit removing CHANGES.txt
in
I started looking at this yesterday, MAPREDUCE CHANGES.txt is completely
broken. I'll try to fix it and then send out a note once I am done.
Thanks,
+Vinod
On Apr 1, 2013, at 11:46 PM, Vinod Kumar Vavilapalli wrote:
>
> I've been looking at YARN and it seems to be fine. I presume common and hd
I've been looking at YARN and it seems to be fine. I presume common and hdfs
too.
MR clearly has issues. Have to manually fix it. Will do something tomorrow
first thing.
Thanks,
+Vinod Kumar Vavilapalli
On Apr 1, 2013, at 3:53 PM, Alejandro Abdelnur wrote:
> while trying to commit MAPREDUCE-
