Hi Arun,
Some bug fixes about MapReduce should be included in next release.
MAPREDUCE-5221 should be merged because it's a lost feature of MRv2
compared to MRv1.
MAPREDUCE-5358 and MAPREDUCE-5335 are very trivial fixes, so it can be
merged immediately.
# I sent the previous email only to
Steve Loughran created HADOOP-9693:
--
Summary: Shell should add a probe for OSX
Key: HADOOP-9693
URL: https://issues.apache.org/jira/browse/HADOOP-9693
Project: Hadoop Common
Issue Type:
DeepakVohra created HADOOP-9695:
---
Summary: double values not Double values
Key: HADOOP-9695
URL: https://issues.apache.org/jira/browse/HADOOP-9695
Project: Hadoop Common
Issue Type: Bug
DeepakVohra created HADOOP-9694:
---
Summary: getCombinerOutput method return value
Key: HADOOP-9694
URL: https://issues.apache.org/jira/browse/HADOOP-9694
Project: Hadoop Common
Issue Type:
DeepakVohra created HADOOP-9696:
---
Summary: getTaskAttemptId returns task attempt id not task id
Key: HADOOP-9696
URL: https://issues.apache.org/jira/browse/HADOOP-9696
Project: Hadoop Common
DeepakVohra created HADOOP-9697:
---
Summary: Mapper example
Key: HADOOP-9697
URL: https://issues.apache.org/jira/browse/HADOOP-9697
Project: Hadoop Common
Issue Type: Bug
Reporter:
Daryn Sharp created HADOOP-9698:
---
Summary: RPCv9 client must honor server's SASL negotiate response
Key: HADOOP-9698
URL: https://issues.apache.org/jira/browse/HADOOP-9698
Project: Hadoop Common
Mark Miller created HADOOP-9699:
---
Summary: org.apache.hadoop.fs.FileUtil#canRead and canWrite should
return false on SecurityExceptions.
Key: HADOOP-9699
URL: https://issues.apache.org/jira/browse/HADOOP-9699
Binglin Chang created HADOOP-9700:
-
Summary: Snapshot support for distcp
Key: HADOOP-9700
URL: https://issues.apache.org/jira/browse/HADOOP-9700
Project: Hadoop Common
Issue Type: Bug
Steve Loughran created HADOOP-9701:
--
Summary: mvn site generation warning of an ambiguous link in
Compatibility.apt
Key: HADOOP-9701
URL: https://issues.apache.org/jira/browse/HADOOP-9701
Project:
We should get these in, looking at them now.
Thanks,
+Vinod
On Jun 28, 2013, at 12:03 PM, Hitesh Shah wrote:
Hi Arun,
From a YARN perspective, YARN-791 and YARN-727 are 2 jiras that may
potentially change the apis. They can implemented in a backward compat
fashion if committed after
I committed MAPREDUCE-5358 to branch-2 but did not commit it to
branch-2.1-beta since it wasn't a blocker and Arun was in the middle of
cutting the release.
Arun, if you feel it's appropriate to put this in branch-2.1-beta feel
free to pull it in or let me know. Thanks!
Jason
On
Thanks, Larry, for starting this conversation (and thanks for the great Summit
meeting summary you sent out a couple of days ago). To weigh in on your
specific discussion points (and renumber them :-))...
1. Are there additional components that would be required for a Hadoop SSO
service?
Not
Hi Larry,
Thanks for the update. Good to see that with this update we are now aligned on
most points.
I have also updated our TokenAuth design in HADOOP-9392. The new revision
incorporates feedback and suggestions in related discussion with the community,
particularly from Microsoft and
Suresh Srinivas created HADOOP-9702:
---
Summary: FileSystem should fail create call with OverWrite and
Append flags
Key: HADOOP-9702
URL: https://issues.apache.org/jira/browse/HADOOP-9702
Project:
+1
- Verified checksums and signatures
- Booted single-node cluster from binary tarball and ran a few sample jobs
- Built source distribution, installed a single-node cluster and ran a
few sample jobs
Jason
On 07/01/2013 12:20 PM, Thomas Graves wrote:
I've created a release candidate (RC0)
Hi Kai -
I think that I need to clarify something…
This is not an update for 9533 but a continuation of the discussions that are
focused on a fresh look at a SSO for Hadoop.
We've agreed to leave our previous designs behind and therefore we aren't
really seeing it as an HSSO layered on top of
Thanks, Brian!
Look at that - the power of collaboration - the numbering is correct already!
;-)
I am inclined to agree that we should start with the Hadoop SSO Tokens and am
leaning toward a new jira that leaves behind the cruft but I don't feel very
strongly about it being new.
I do feel
Hi Larry,
Of course I'll let Kai speak for himself. However, let me point out that,
while the differences between the competing JIRAs have been reduced for
sure, there were some key differences that didn't just disappear.
Subsequent discussion will make that clear. I also disagree with your
Thanks for the excellent summary Larry,
Questions for the group:
I have taken a quick look at how pluggable token validation could be added to
the RPC endpoints:
- Are there any current approaches that I should examined before I
continue with my investigation?
- For server Auth;
Hi Larry,
I participated in the design discussion at Hadoop Summit. I do not remember
there was any discussion of abandoning the current JIRAs which tracks a lot of
good input from others in the community and important for us to consider as we
move forward with the work. Recommend we continue
21 matches
Mail list logo
