Just to close the loop on this a bit ...
Windows always triggers the 'native-win' profile because winutils is
currently required to actually use Apache Hadoop on that platform. On other
platforms, the 'native' profile is optional since their is enough support in
the JDK to at least
Allen Wittenauer created HADOOP-14817:
-
Summary: shelldocs fails mvn site
Key: HADOOP-14817
URL: https://issues.apache.org/jira/browse/HADOOP-14817
Project: Hadoop Common
Issue Type: Bug
Allen Wittenauer created HADOOP-14816:
-
Summary: Update Dockerfile to use Xenial
Key: HADOOP-14816
URL: https://issues.apache.org/jira/browse/HADOOP-14816
Project: Hadoop Common
Issue
Allen Wittenauer created HADOOP-14815:
-
Summary: s3guard usage calls function incorrectly
Key: HADOOP-14815
URL: https://issues.apache.org/jira/browse/HADOOP-14815
Project: Hadoop Common
> On Aug 28, 2017, at 12:41 PM, Jason Lowe wrote:
>
> I think this gets back to the "if it's worth committing" part.
This brings us back to my original question:
"Doesn't this place an undue burden on the contributor with the first
incompatible patch to prove
> On Aug 25, 2017, at 1:23 PM, Jason Lowe <jl...@oath.com> wrote:
>
> Allen Wittenauer wrote:
>
> > Doesn't this place an undue burden on the contributor with the first
> > incompatible patch to prove worthiness? What happens if it is decided
> On Aug 25, 2017, at 10:36 AM, Andrew Wang wrote:
> Until we need to make incompatible changes, there's no need for
> a Hadoop 4.0 version.
Some questions:
Doesn't this place an undue burden on the contributor with the first
incompatible patch to prove
> On Aug 25, 2017, at 10:00 AM, Steve Loughran wrote:
>
> Catching up on this. Looks like I don't have a hadoop-aws profile, which
> explains a lot, doesn't it.
Yes. This is exactly the type of failure I'd expect.
> How do those profiles get created/copied in?
We should avoid turning this into a replay of Apache Hadoop 2.6.0 (and
to a lesser degree, 2.7.0 and 2.8.0) where a bunch of last minute
“experimental” features derail stability for a significantly long period of
time.
> On Aug 22, 2017, at 6:00 AM, Steve Loughran wrote:
>
>
> I'm having problems getting the s3 classpath setup on the CLI & am trying to
> work out what I'm doing wrong.
>
>
> without setting things up, you can't expect to talk to blobstores
>
> hadoop fs -ls
Allen Wittenauer created HADOOP-14781:
-
Summary: Clarify that HADOOP_CONF_DIR shouldn't actually be set in
hadoop-env.sh
Key: HADOOP-14781
URL: https://issues.apache.org/jira/browse/HADOOP-14781
> On Aug 14, 2017, at 5:36 AM, Brahma Reddy Battula
> wrote:
>
> How about let this comment on Jira if there is any failure(compile/Test)..?
> so that corresponding Jira reporter/committer can look into it(can
> reduce/avoid pre-commit failures..?).
>
For more details, see https://builds.apache.org/job/hadoop-trunk-win/155/
[Aug 8, 2017 10:37:47 PM] (stevel) HADOOP-14715. TestWasbRemoteCallHelper
failing. Contributed by Esfandiar
[Aug 8, 2017 11:33:18 PM] (wheat9) HADOOP-14598. Blacklist Http/HttpsFileSystem
in
[Aug 8, 2017 11:48:29 PM]
> On Aug 9, 2017, at 5:04 AM, Ewan Higgs wrote:
> Is Jenkins even building these?
No, Jenkins is not currently running any of the ITs (this one and the
ones in hadoop-aws). Probably worth pointing out that a large chunk of the
unit tests are really misclassified
It’s probably worth pointing out that as soon as the
native-maven-plugin gets an update, we’ll be able to have a longer path.
Unfortunately, like leveldbjni-all, it’s effectively dead as far as updates;
the fix was committed in 2014 and there hasn’t been an update since.
As a
Something else to consider. The main hadoop repo has precommit support. I
could easily see a quick and dirty maven pom.xml and dockerfile put in place to
build the website against “patches” uploaded to JIRA or github.
-
To
> On Aug 8, 2017, at 12:36 AM, Akira Ajisaka wrote:
>
> Now I'm okay with not creating another repo.
> I'm thinking the following procedures may work:
>
> 1. Create ./asf-site directory
> 2. Add the content of https://github.com/elek/hadoop-site-proposal to the
>
> On Aug 7, 2017, at 3:53 AM, Akira Ajisaka wrote:
>
>
> I'll ask INFRA to create a git repository if there are no objections.
There's no need to create a git repo. They just need to know to pull
the website from the asf-site branch.
For more details, see https://builds.apache.org/job/hadoop-trunk-win/146/
[Aug 2, 2017 4:25:19 PM] (yufei) YARN-6895. [FairScheduler] Preemption
reservation may cause regular
-1 overall
The following subsystems voted -1:
unit
The following subsystems are considered long running:
[
https://issues.apache.org/jira/browse/HADOOP-14725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-14725.
---
Resolution: Duplicate
> hadoop-aws parallel tests do not work under Wind
Allen Wittenauer created HADOOP-14725:
-
Summary: hadoop-aws parallel tests do not work under Windows
Key: HADOOP-14725
URL: https://issues.apache.org/jira/browse/HADOOP-14725
Project: Hadoop
Allen Wittenauer created HADOOP-14724:
-
Summary: Get a daily QBT run for Windows
Key: HADOOP-14724
URL: https://issues.apache.org/jira/browse/HADOOP-14724
Project: Hadoop Common
Issue
ot;
>
> Thanks,
> --Konst
>
> On Mon, Jul 31, 2017 at 4:51 PM, Allen Wittenauer
> <a...@effectivemachines.com> wrote:
>
> > On Jul 31, 2017, at 4:18 PM, Andrew Wang <andrew.w...@cloudera.com> wrote:
> >
> > Forking this off to not distract from r
> On Jul 31, 2017, at 4:18 PM, Andrew Wang wrote:
>
> Forking this off to not distract from release activities.
>
> I filed https://issues.apache.org/jira/browse/LEGAL-323 to get clarity on the
> matter. I read the entire webpage, and it could be improved one way or
For more details, see https://builds.apache.org/job/hadoop-trunk-win/141/
[Jul 31, 2017 2:09:13 AM] (aajisaka) YARN-5728.
TestMiniYarnClusterNodeUtilization.testUpdateNodeUtilization
[Jul 31, 2017 5:08:30 AM] (aajisaka) HADOOP-14690. RetryInvocationHandler
should override toString().
[Jul 31,
> On Jul 31, 2017, at 11:20 AM, Konstantin Shvachko
> wrote:
>
> https://wiki.apache.org/hadoop/HowToReleasePreDSBCR
FYI:
If you are using ASF Jenkins to create an ASF release artifact,
it's pretty much an automatic vote failure as any such
Allen Wittenauer created HADOOP-14696:
-
Summary: common's parallel tests don't work for Windows
Key: HADOOP-14696
URL: https://issues.apache.org/jira/browse/HADOOP-14696
Project: Hadoop Common
For more details, see https://builds.apache.org/job/hadoop-trunk-win/136/
HADOOP-1466. Flexible Visual Studio support
-1 overall
The following subsystems voted -1:
unit
The following subsystems are considered long running:
(runtime bigger than 1h 00m 00s)
unit
Specific tests:
Allen Wittenauer created HADOOP-14692:
-
Summary: Upgrade Apache Rat
Key: HADOOP-14692
URL: https://issues.apache.org/jira/browse/HADOOP-14692
Project: Hadoop Common
Issue Type: Bug
I've noticed that in almost all of the (official) documentation, it's written
that in order to build on Windows the maven command should be some form of:
mvn package -Pdist,native-win -DskipTests
The one constant is that the native-win profile is always listed. What's
interesting is that
gt;> On Fri, Jul 21, 2017 at 6:24 PM, Konstantin Shvachko <
> >> shv.had...@gmail.com> wrote:
> >>
> >>> What stuff? Is there a jira?
> >>> It did work like a week ago. Is it a new Yetus requirement.
> >>> Anyways I can commit a change t
> On Jul 22, 2017, at 11:31 PM, Brahma Reddy Battula
> wrote:
>
> AFAIK, Patch install(i mean,mvn install) will not run all the projects hence
> you didn't seen this failure.
Correct. By design, precommit only runs the test suite against the maven
modules
> On Jul 22, 2017, at 10:12 PM, Brahma Reddy Battula
> wrote:
>
> FYI..After Jian he comment on YARN-6804,I reverted. Now trunk build will pass.
>
Yup:
https://s.apache.org/S6yd
-
To
The "update the maven snapshot repo after a commit then update the JIRA issue
on the build status" job caught it (https://s.apache.org/bXUp) but looks like
it's feedback and the -1 on the mvninstall after it was ignored. *shrugs*
> On Jul 22, 2017, at 3:33 PM, Bokor Andras
Allen Wittenauer created HADOOP-14673:
-
Summary: Remove leftover hadoop_xml_escape from functions
Key: HADOOP-14673
URL: https://issues.apache.org/jira/browse/HADOOP-14673
Project: Hadoop Common
Allen Wittenauer created HADOOP-14670:
-
Summary: Increase minimum cmake version for all platforms
Key: HADOOP-14670
URL: https://issues.apache.org/jira/browse/HADOOP-14670
Project: Hadoop Common
Allen Wittenauer created HADOOP-14664:
-
Summary: TestCodec's sequenceFileCodecTest doesn't use correct
directory
Key: HADOOP-14664
URL: https://issues.apache.org/jira/browse/HADOOP-14664
Project
It looks like HADOOP-13578 added Facebook's zstd compression codec.
Unfortunately, that codec is using the same 3-clause BSD (LICENSE file) +
patent grant license (PATENTS file) that React is using and RocksDB was using.
Should that code get reverted?
Allen Wittenauer created HADOOP-14663:
-
Summary: Switch to OpenClover
Key: HADOOP-14663
URL: https://issues.apache.org/jira/browse/HADOOP-14663
Project: Hadoop Common
Issue Type
Allen Wittenauer created HADOOP-14602:
-
Summary: allow custom release notes/changelog during create-release
Key: HADOOP-14602
URL: https://issues.apache.org/jira/browse/HADOOP-14602
Project
This is just a heads up.
The Apache Yetus community is debating removing the maven eclipse
plug-in testing support from precommit. (Given that Apache Hadoop is currently
rigged up to always run Yetus' master for testing purposes, this means Hadoop
will see the removal
Allen Wittenauer created HADOOP-14378:
-
Summary: Upgrade to maven-site-plugin 3.6
Key: HADOOP-14378
URL: https://issues.apache.org/jira/browse/HADOOP-14378
Project: Hadoop Common
Issue
Allen Wittenauer created HADOOP-14375:
-
Summary: Remove tomcat support from hadoop-functions.sh
Key: HADOOP-14375
URL: https://issues.apache.org/jira/browse/HADOOP-14375
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-13364.
---
Resolution: Duplicate
Assignee: (was: Yulei Li)
> Varia
[
https://issues.apache.org/jira/browse/HADOOP-13364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer reopened HADOOP-13364:
---
> Variable HADOOP_LIBEXEC_DIR must be quoted in bin/hadoop line
Is there any reason to not Close -alpha1+resolved state JIRAs? It's been quite
a while and those definitely should not getting re-opened anymore. What about
-alpha2's that are also resolved?
-
To unsubscribe, e-mail:
> On May 1, 2017, at 2:27 PM, Andrew Wang wrote:
> I believe I asked about this on dev-yetus a while back. I'd prefer that the
> presence of the fix version be sufficient to indicate whether a JIRA is
> included in a release branch. Yetus requires that the JIRA be
Allen Wittenauer created HADOOP-14366:
-
Summary: maven upgrade broke start-build-env.sh
Key: HADOOP-14366
URL: https://issues.apache.org/jira/browse/HADOOP-14366
Project: Hadoop Common
Allen Wittenauer created HADOOP-14364:
-
Summary: refresh changelog/release notes with newer Apache Yetus
build
Key: HADOOP-14364
URL: https://issues.apache.org/jira/browse/HADOOP-14364
Project
> On Apr 25, 2017, at 12:35 AM, Akira Ajisaka wrote:
> > Maybe we should create a jira to track this?
>
> I think now either way (reopen or create) is fine.
>
> Release doc maker creates change logs by fetching information from JIRA, so
> reopening the tickets should be
[
https://issues.apache.org/jira/browse/HADOOP-12607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-12607.
---
Resolution: Cannot Reproduce
> wrong pid dir results in cat error messages dur
[
https://issues.apache.org/jira/browse/HADOOP-12940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer reopened HADOOP-12940:
---
It's effectively the same thing. Let's see if this patch applies still.
>
> On Apr 19, 2017, at 10:52 AM, Wei-Chiu Chuang wrote:
> That sounds scary. Would you mind to share the list of bugs that spotbugs
> found? Sounds like some of them may warrant new blockers jiras for Hadoop 3.
I've added the list to the JIRA.
Hey gang.
HADOOP-14316 enables the spotbugs back-end for the findbugs front-end.
Spotbugs (https://spotbugs.github.io/) is the fork of findbugs that the
community and some of the major contributors have made to move findbugs
forward. It is geared towards JDK8 and JDK9.
Allen Wittenauer created HADOOP-14316:
-
Summary: Switch from FindBugs to Spotbugs
Key: HADOOP-14316
URL: https://issues.apache.org/jira/browse/HADOOP-14316
Project: Hadoop Common
Issue
Looks like someone reset HEAD back to Mar 31.
Sent from my iPad
> On Apr 16, 2017, at 12:08 AM, Apache Jenkins Server
> wrote:
>
> For more details, see
> https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/378/
>
>
>
>
>
> -1 overall
>
>
> The
> On Apr 13, 2017, at 11:13 PM, Arun Suresh wrote:
>
> Yup,
>
> YARN Pre-Commit tests are having the same problem as well.
> Is there anything that can be done to fix this ? Ping Yetus folks (Allen /
> Sean)
https://issues.apache.org/jira/browse/HADOOP-14311
Allen Wittenauer created HADOOP-14311:
-
Summary: Add python2.7-dev to Dockerfile
Key: HADOOP-14311
URL: https://issues.apache.org/jira/browse/HADOOP-14311
Project: Hadoop Common
Issue
ng <andrew.w...@cloudera.com> wrote:
> What's the current contract for `hadoop classpath`? Would it be safer to
> introduce `hadoop userclasspath` or similar for this behavior?
>
> I'm betting that changing `hadoop classpath` will lead to some breakages,
> so I'd prefer to make t
This morning I had a bit of a shower thought:
With the new shaded hadoop client in 3.0, is there any reason the
default classpath should remain the full blown jar list? e.g., shouldn’t
‘hadoop classpath’ just return configuration, user supplied bits (e.g.,
> On Mar 28, 2017, at 5:09 PM, Chris Douglas wrote:
>
> I haven't seen data identifying PB as a bottleneck, but the
> non-x86/non-Linux and dev setup arguments may make this worthwhile. -C
FWIW, we have the same problem with leveldbjni-all. (See the ASF
Hey gang.
Could I get a quick review of HADOOP-14202? This changes a few things:
* Makes the rest of the _USER vars consistent with the other changes in
trunk (e.g., HADOOP_SECURE_DN_USER becomes HDFS_DATANODE_SECURE_USER)
* deprecation warnings as necessary
*
Just a heads up. Looks like some removed the Finish Date off of 2.8.0 in JIRA.
It needs to be put back to match what is in the artifacts that we voted on.
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For
Allen Wittenauer created HADOOP-14224:
-
Summary: add dnsutils to Dockerfile to aid in debugging maven repo
failures
Key: HADOOP-14224
URL: https://issues.apache.org/jira/browse/HADOOP-14224
> On Mar 21, 2017, at 10:12 AM, Andrew Wang wrote:
>
> I poked around a bit. The 3.0.0-alpha2 binary tarball is only 246M and has
> more changes than 2.8.0.
Not to disclaim any other potential issues, but it's worth noting 3.x de-dupes
jar files as part of the
Allen Wittenauer created HADOOP-14202:
-
Summary: fix jsvc/secure user inconsistencies
Key: HADOOP-14202
URL: https://issues.apache.org/jira/browse/HADOOP-14202
Project: Hadoop Common
> On Mar 9, 2017, at 2:15 PM, Andrew Wang wrote:
>
> H9 is again eating our builds.
>
H0: https://builds.apache.org/job/PreCommit-HDFS-Build/18652/console
H6: https://builds.apache.org/job/PreCommit-HDFS-Build/18646/console
> On Mar 8, 2017, at 2:53 PM, Anu Engineer wrote:
>
> Agreed, but I was under the impression that we would kill the container under
> OOM conditions and not the whole base machine.
We do not run our docker containers under a cgroup.
> On Mar 8, 2017, at 1:54 PM, Allen Wittenauer <a...@effectivemachines.com>
> wrote:
>
> This is already possible:
> * don’t use —asfrelease
> * use —sign, —native, and, if appropriate for your platform,
> —docker and —dockercache
> On Mar 8, 2017, at 2:21 PM, Anu Engineer wrote:
>
> Hi Allen,
>> Likely something in the HDFS-7240 branch or with this patch that's
>> doing Bad Things (tm).
>
> Thanks for bringing this to my attention, But I am surprised that a mvn
> command is able to
> On Mar 8, 2017, at 10:55 AM, Marton Elek wrote:
>
> I think the main point here is the testing of the release script, not the
> creation of the official release.
… except the Hadoop PMC was doing exactly this from 2.3.0 up until
recently. Which means we have
> On Mar 8, 2017, at 12:04 PM, Allen Wittenauer <a...@effectivemachines.com>
> wrote:
>
>
>> On Mar 8, 2017, at 9:34 AM, Sean Busbey <bus...@cloudera.com> wrote:
>>
>> Is this HADOOP-13951?
>
> Almost certainly. Here's the run that br
> On Mar 8, 2017, at 9:34 AM, Sean Busbey wrote:
>
> Is this HADOOP-13951?
Almost certainly. Here's the run that broke it again:
https://builds.apache.org/job/PreCommit-HDFS-Build/18591
Likely something in the HDFS-7240 branch or with this patch that's
> On Mar 7, 2017, at 2:51 PM, Andrew Wang wrote:
> I think it'd be nice to
> have a nightly Jenkins job that builds an RC,
Just a reminder that any such build cannot be used for an actual
release:
> On Mar 6, 2017, at 1:57 PM, Andrew Wang wrote:
>
> I'll leave it there so it's ready for next time. If this keeps happening on
> H9, then I'm going to ask infra to reimage it. FWIW I haven't seen this on
> our internal unit test runs, so it points to an H9-specific
> On Mar 6, 2017, at 1:17 PM, Andrew Wang wrote:
>
> Do you have a link to your old job somewhere?
Nope, but it’s trivial to write. single job that only runs on H9 that
removes that other job’s workspace dir. You can also try using the “Wipe out
current
> On Mar 6, 2017, at 11:27 AM, Andrew Wang wrote:
> Looks like H9 is having problems cleaning the workspace, leading to a lot
> of silent precommit failures. I filed this INFRA JIRA:
> https://issues.apache.org/jira/browse/INFRA-13618
Have we tried writing a job that
[
https://issues.apache.org/jira/browse/HADOOP-13119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-13119.
---
Resolution: Fixed
Fix Version/s: 3.0.0-alpha2
Re-resolving
> On Jan 23, 2017, at 8:50 PM, Chris Douglas wrote:
>
> Thanks for all your work on this, Andrew. It's great to see the 3.x
> series moving forward.
>
> If you were willing to modify the release notes and add the LICENSE to
> the jar, we don't need to reset the clock
> On Jan 21, 2017, at 7:08 PM, Karthik Kambatla wrote:
>
> 3. RM: some method to madness. Junping, for instance, is trying to roll
> a release with 2300 patches. It is a huge time investment. (Thanks again,
> Junping.) Smaller releases are easier to manage. A target
> On Jan 22, 2017, at 9:05 PM, Allen Wittenauer <a...@effectivemachines.com>
> wrote:
>
>
>
>
>
>> On Jan 20, 2017, at 2:36 PM, Andrew Wang <andrew.w...@cloudera.com> wrote:
>>
>> http://home.apache.org/~wang/3.0.0-alpha2-RC0/
>
>
> On Jan 20, 2017, at 2:36 PM, Andrew Wang wrote:
>
> http://home.apache.org/~wang/3.0.0-alpha2-RC0/
There are quite a few JIRA issues that need release notes.
-
To unsubscribe, e-mail:
Allen Wittenauer created HADOOP-14016:
-
Summary: add license and notice verifaction to create-release
Key: HADOOP-14016
URL: https://issues.apache.org/jira/browse/HADOOP-14016
Project: Hadoop
If you ran mvn clean at any point in your repo between create-release and mvn
deploy, you'll need to start at running create-release again. create-release
leaves things in a state that mvn deploy should be ready to go, with no clean
necessary.
> On Jan 20, 2017, at 11:12 AM, Junping Du
Allen Wittenauer created HADOOP-14011:
-
Summary: fix the remaining shelldoc errors
Key: HADOOP-14011
URL: https://issues.apache.org/jira/browse/HADOOP-14011
Project: Hadoop Common
Issue
Allen Wittenauer created HADOOP-14010:
-
Summary: Fix the remaining shellcheck errors
Key: HADOOP-14010
URL: https://issues.apache.org/jira/browse/HADOOP-14010
Project: Hadoop Common
Allen Wittenauer created HADOOP-14009:
-
Summary: dev-support/bin should use hadoop-functions.sh
Key: HADOOP-14009
URL: https://issues.apache.org/jira/browse/HADOOP-14009
Project: Hadoop Common
Allen Wittenauer created HADOOP-14008:
-
Summary: Upgrade to Apache Yetus 0.4.0
Key: HADOOP-14008
URL: https://issues.apache.org/jira/browse/HADOOP-14008
Project: Hadoop Common
Issue Type
> On Jan 18, 2017, at 11:21 AM, Chris Trezzo wrote:
>
> Thanks Sangjin for pushing this forward! I have a few questions:
These are great questions, because I know I'm not seeing a whole lot of
substance in this vote. The way to EOL software in the open source
Allen Wittenauer created HADOOP-13964:
-
Summary: Remove vestigal template directory creation
Key: HADOOP-13964
URL: https://issues.apache.org/jira/browse/HADOOP-13964
Project: Hadoop Common
Allen Wittenauer created HADOOP-13957:
-
Summary: prevent bad PATHs
Key: HADOOP-13957
URL: https://issues.apache.org/jira/browse/HADOOP-13957
Project: Hadoop Common
Issue Type: New
Allen Wittenauer created HADOOP-13952:
-
Summary: tools dependency hooks are throwing errors
Key: HADOOP-13952
URL: https://issues.apache.org/jira/browse/HADOOP-13952
Project: Hadoop Common
Allen Wittenauer created HADOOP-13896:
-
Summary: disribution tarball is mising almost all of the hadoop
jars
Key: HADOOP-13896
URL: https://issues.apache.org/jira/browse/HADOOP-13896
Project
> On Nov 7, 2016, at 11:29 AM, Ravi Prakash wrote:
>
> I have a preference for d) Contributed by XXX.
>
> Wouldn't signed-off require the commit to come from the contributor? What
> about people who submit patch files?
If the patches are built with 'git
> On Nov 1, 2016, at 4:00 AM, Brahma Reddy Battula
> wrote:
> Thanks for information. Seems to be challenge to get it done. Can we try to
> get dedicated machine for this..?
We have one. What we don't have is someone dedicated enough to keep it
> On Oct 27, 2016, at 8:20 PM, Brahma Reddy Battula
> wrote:
>
> As we supporting the Hadoop in windows, I feel, we should have pre-commit
> build in windows( atleast in qbt).
I actually tried to get Apache Yetus testing Apache Hadoop on the
[
https://issues.apache.org/jira/browse/HADOOP-13741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-13741.
---
Resolution: Duplicate
> The shell scripts output error if the directory of had
[
https://issues.apache.org/jira/browse/HADOOP-13669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer reopened HADOOP-13669:
---
bq. Findbugs warnings are false alarm, since the exception is thrown.
...
bq
> 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
Allen Wittenauer created HADOOP-13673:
-
Summary: Update sbin/start-* and sbin/stop-* to be smarter
Key: HADOOP-13673
URL: https://issues.apache.org/jira/browse/HADOOP-13673
Project: Hadoop Common
101 - 200 of 1185 matches
Mail list logo