> On Oct 6, 2016, at 1:39 PM, Akira Ajisaka wrote:
>
> > It wasn't 'renamed' to jenkins, prior releases were actually built by and
> > on the Jenkins infrastructure. Which was a very very bad idea: it's
> > insecure and pretty much against ASF policy.
>
> Sorry for the confusion. I should no
Xiao Chen created HADOOP-13693:
--
Summary: Make the SPNEGO initialization OPTIONS message in kms
audit log more admin-friendly
Key: HADOOP-13693
URL: https://issues.apache.org/jira/browse/HADOOP-13693
Pro
Chris Nauroth created HADOOP-13692:
--
Summary: hadoop-aws should declare explicit dependency on Jackson
2 jars to prevent classpath conflicts.
Key: HADOOP-13692
URL: https://issues.apache.org/jira/browse/HADOOP-13
Sangjin Lee created HADOOP-13691:
Summary: remove build person and date from various hadoop UI
Key: HADOOP-13691
URL: https://issues.apache.org/jira/browse/HADOOP-13691
Project: Hadoop Common
I think it's a good idea. We can still have the underlying data (in
*-version.properties) but we can consider removing the date and the build
person from the web UI. I'll file a JIRA to consider the idea.
I would greatly appreciate it if you folks can take a little time to take
the RC1 for a spin
I don't think it's a blocker, though I wonder what the point of that date
and attribution are on the WebUI.
Maybe file a follow-on JIRA to remove it for the future?
On Thu, Oct 6, 2016 at 3:09 PM, Sangjin Lee wrote:
> I looked into building it on jenkins earlier, but it appears that this
> jenk
I looked into building it on jenkins earlier, but it appears that this
jenkins job is busted (at least for 2.6.x):
https://builds.apache.org/job/HADOOP2_Release_Artifacts_Builder/
I don't have access to the job configuration, so I'm unable to fix it atm.
That said, I do think Allen has a point. I
[
https://issues.apache.org/jira/browse/HADOOP-9244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter resolved HADOOP-9244.
---
Resolution: Duplicate
I've been working on HADOOP-10075 to update Jetty 6.x to 9.x, and part
> It wasn't 'renamed' to jenkins, prior releases were actually built by
and on the Jenkins infrastructure. Which was a very very bad idea: it's
insecure and pretty much against ASF policy.
Sorry for the confusion. I should not have used the word 'rename'.
What I meant is that "would you change
[
https://issues.apache.org/jira/browse/HADOOP-11513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mingliang Liu resolved HADOOP-11513.
Resolution: Cannot Reproduce
Feel free to re-open if it happens again. Thanks.
> Artifact
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-ppc/116/
[Oct 5, 2016 2:02:11 PM] (stevel) HADOOP-12667 s3a to support
createNonRecursive API. Contributed by Sean
[Oct 5, 2016 5:52:50 PM] (jing9) HDFS-10826. Correctly report missing EC blocks
in FSCK. Contribute
+1 ( non- binding)
--Downloaded source and built from it.
--Installed 3 node cluster with HA deployed.
—Ran sample MR jobs and tested with basics operations.
— Integrated JCarder tool to find any potential deadlock cycles. And did not
observe any potential cycles.
Thanks & Regards
Rohith Sharm
> On Oct 5, 2016, at 10:35 PM, Akira Ajisaka wrote:
> Can we rename it?
>
> AFAIK, hadoop releases were built by hortonmu in 2014 and was renamed to
> jenkins.
That's not how that works.
It's literally storing the id of the person who built the classes. It
wasn't 'renamed' t
For more details, see
https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/186/
[Oct 5, 2016 10:01:38 AM] (vvasudev) YARN-5704. Provide config knobs to control
enabling/disabling new/work
[Oct 5, 2016 11:41:08 AM] (aajisaka) HADOOP-13685. Document -safely option of
rm command. Contrib
Yiqun Lin created HADOOP-13690:
--
Summary: Fix typos in core-default.xml
Key: HADOOP-13690
URL: https://issues.apache.org/jira/browse/HADOOP-13690
Project: Hadoop Common
Issue Type: Bug
15 matches
Mail list logo
