ts. Right now, the proposed PMC would be (alphabetical by last
> name):
>
> * Andrew Bayer (ASF member, incubator pmc, bigtop pmc, flume pmc, jclouds
> pmc, sqoop pmc, all around Jenkins expert)
> * Sean Busbey (ASF member, accumulo pmc, hbase pmc)
> * Nick Dimiduk (hbase pmc, phoenix
On Jun 12, 2015, at 1:03 PM, Alan Burlison wrote:
> On 14/05/2015 18:41, Chris Nauroth wrote:
>
>> As a reminder though, the community probably would want to see a strong
>> justification for the upgrade in terms of features or performance or
>> something else. Right now, I'm not seeing a sign
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 a timely manner. The difference between
> trunk and branch-2 is sufficient to justify periodic jenkins test and even
> pre-commit test
On Jun 12, 2015, at 12:37 AM, Sitaraman Vilayannur
wrote:
> Hi,
> What is the limit on the number of properties that can be set using
> set(String s1, String s2) on the Configuration object for hadoop?
> Is this limit configurable if so what is the maximum that can be set?
It's a "tot
[
https://issues.apache.org/jira/browse/HADOOP-12025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-12025.
---
Resolution: Won't Fix
> test-patch.sh needs per-project, per-branch mav
[
https://issues.apache.org/jira/browse/HADOOP-12024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-12024.
---
Resolution: Won't Fix
> test-patch.sh should provide a way to override the
On May 28, 2015, at 11:29 AM, Sangjin Lee wrote:
> Thanks Chris and Allen for the info! Yes, we can use HADOOP_PREFIX
> until/unless HADOOP-11393 is resolved.
>
> Just to clarify, we're not setting HADOOP_HOME/HADOOP_PREFIX in our
> *-env.sh; we simply use them. I don't know that it is always f
On May 28, 2015, at 9:36 AM, Sangjin Lee wrote:
> Hi folks,
>
> I noticed this while setting up a cluster based on the current trunk. It
> appears that setting HADOOP_HOME is now done much later (in
> hadoop_finalize) than branch-2. Importantly this is set *after*
> hadoop-env.sh (or yarn-env.s
Allen Wittenauer created HADOOP-12036:
-
Summary: Consolidate all of the cmake extensions in one directory
Key: HADOOP-12036
URL: https://issues.apache.org/jira/browse/HADOOP-12036
Project: Hadoop
Allen Wittenauer created HADOOP-12031:
-
Summary: test-patch.sh should have an xml plugin
Key: HADOOP-12031
URL: https://issues.apache.org/jira/browse/HADOOP-12031
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-9584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-9584.
--
Closing as stale, incomplete
> fix findbugs warni
Allen Wittenauer created HADOOP-12027:
-
Summary: need a maven property for bzip2 headers
Key: HADOOP-12027
URL: https://issues.apache.org/jira/browse/HADOOP-12027
Project: Hadoop Common
Allen Wittenauer created HADOOP-12025:
-
Summary: test-patch.sh needs per-project, per-branch maven repos
Key: HADOOP-12025
URL: https://issues.apache.org/jira/browse/HADOOP-12025
Project: Hadoop
Allen Wittenauer created HADOOP-12024:
-
Summary: test-patch.sh should provide a way to override the
default dockerfile
Key: HADOOP-12024
URL: https://issues.apache.org/jira/browse/HADOOP-12024
Allen Wittenauer created HADOOP-12023:
-
Summary: test-patch.sh triggered full hdfs unit tests when it
shouldn't
Key: HADOOP-12023
URL: https://issues.apache.org/jira/browse/HADOOP-12023
Pr
Allen Wittenauer created HADOOP-12022:
-
Summary: fix site -Pdocs in hadoop-project-dist
Key: HADOOP-12022
URL: https://issues.apache.org/jira/browse/HADOOP-12022
Project: Hadoop Common
Allen Wittenauer created HADOOP-12004:
-
Summary: test-patch breaks with reexec in certain situations
Key: HADOOP-12004
URL: https://issues.apache.org/jira/browse/HADOOP-12004
Project: Hadoop
Allen Wittenauer created HADOOP-12000:
-
Summary: cannot use --java-home in test-patch
Key: HADOOP-12000
URL: https://issues.apache.org/jira/browse/HADOOP-12000
Project: Hadoop Common
Allen Wittenauer created HADOOP-11994:
-
Summary: smart-apply-patch wrongly assumes that git is infalliable
Key: HADOOP-11994
URL: https://issues.apache.org/jira/browse/HADOOP-11994
Project: Hadoop
Hey gang.
I promised a post-mortem, but I got distracted with making everyone's
lives miserable with new test-patch code. Luckily my coworker Barbara (who
some of you met!) wrote some wrap up info about it on our corporate blog,
including some interesting stats….
htt
[
https://issues.apache.org/jira/browse/HADOOP-6700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-6700.
--
Resolution: Fixed
> Hadoop commands guide should include examp
[
https://issues.apache.org/jira/browse/HADOOP-8364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-8364.
--
Resolution: Won't Fix
Closing as Won't Fix given development on br
[
https://issues.apache.org/jira/browse/HADOOP-7723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-7723.
--
Resolution: Duplicate
Closing as a dupe, based upon HADOOP-11731.
> Automatica
[
https://issues.apache.org/jira/browse/HADOOP-11220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-11220.
---
Resolution: Fixed
Yup. Closing as contained by HADOOP-11746, which rewrote the
On May 13, 2015, at 5:02 AM, Alan Burlison wrote:
> The current version of Protocol Buffers is 2.6.1 but the current version
> required by Hadoop is 2.5.0. Is there any reason for this, or should I log a
> JIRA to get it updated?
The story of protocol buffers is part of a shameful pas
Allen Wittenauer created HADOOP-11965:
-
Summary: determine-flaky-tests needs a summary mode
Key: HADOOP-11965
URL: https://issues.apache.org/jira/browse/HADOOP-11965
Project: Hadoop Common
Allen Wittenauer created HADOOP-11964:
-
Summary: determine-flaky-tests makes invalid test assumptions
Key: HADOOP-11964
URL: https://issues.apache.org/jira/browse/HADOOP-11964
Project: Hadoop
Hi.
A few times now, we’ve run into issues where we weren’t sure what sort
of state the surrounding environment was present when a pre commit patch test
was done. Additionally, there are times when installing or even updating a
component was a challenge. There are some bits
Anyone know if these machines are supposed to be in the Ubuntu pool on
Jenkins? Given they are H-machines, shouldn’t they been in the Hadoop pool?
Right now, we’ve got stuff waiting with zero test slots available while the
Ubuntu pool has slots open that we can’t use. :(
[
https://issues.apache.org/jira/browse/HADOOP-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-11745.
---
Resolution: Fixed
BUILDS-77 was closed, HADOOP-11746 is closed. So closing this
[
https://issues.apache.org/jira/browse/HADOOP-11931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-11931.
---
Resolution: Fixed
Re-committed HADOOP-11881.
> test-patch javac warning ch
Allen Wittenauer created HADOOP-11956:
-
Summary: test-patch.sh's git ref support is fragile
Key: HADOOP-11956
URL: https://issues.apache.org/jira/browse/HADOOP-11956
Project: Hadoop C
On May 11, 2015, at 10:34 AM, Allen Wittenauer wrote:
>
> It’s not a white list; it’s done heuristically. If you read through the
> release notes of HADOOP-11746, you’ll see that it only supports major
> branches. It does not (currently?) support minor or micro branches. (Th
On May 11, 2015, at 10:23 AM, Wangda Tan wrote:
> Hi Hadoop-dev,
>
> Now we are working on branch-2.7 for 2.7.1 release but I found branch-2.7
> may not be added to Jenkins white list. For example: YARN-3434 cannot
> trigger Jenkins build.
>
> Could anybody help to add it?
It’s not a white l
[
https://issues.apache.org/jira/browse/HADOOP-11953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-11953.
---
Resolution: Duplicate
Fix Version/s: (was: 2.7.1)
Duplicate of HADOOP
May we declare this branch dead and just close bugs (but not
necessarily concepts, ideas, etc) with won’t fix? I don’t think anyone has any
intention of working on the 1.3 release, especially given that 1.2.1 was Aug
2013 ….
I guess we need a PMC member to declare a vo
Allen Wittenauer created HADOOP-11936:
-
Summary: Dockerfile references a removed image
Key: HADOOP-11936
URL: https://issues.apache.org/jira/browse/HADOOP-11936
Project: Hadoop Common
Allen Wittenauer created HADOOP-11933:
-
Summary: run test-patch.sh in a docker container under Jenkins
Key: HADOOP-11933
URL: https://issues.apache.org/jira/browse/HADOOP-11933
Project: Hadoop
On May 5, 2015, at 8:10 PM, Allen Wittenauer wrote:
> * We’ll be closing registrations to the Bug Bash on May 6th at
> 3PM Pacific time. So make sure you do it son:
> https://www.eventbrite.com/e/apache-hadoop-global-bug-bash-tickets-16507188445
That
Hey gang!
A couple of things in regards to the Bug Bash on Friday:
* We’ll be closing registrations to the Bug Bash on May 6th at
3PM Pacific time. So make sure you do it son:
https://www.eventbrite.com/e/apache-hadoop-global-bug-bash-tickets-165071884
HDFS, MAPREDUCE, and YARN have been migrated.
Let me know of any issues and I’ll try to get to them as I can. This should be
the end of the Jenkins race conditions for our pre commits! *crosses fingers*
Allen Wittenauer created HADOOP-11926:
-
Summary: test-patch.sh mv does wrong math
Key: HADOOP-11926
URL: https://issues.apache.org/jira/browse/HADOOP-11926
Project: Hadoop Common
Issue
TL;DR:
Heads up: I’m going to hack on these scripts to fix the race
conditions.
Presently, we have a pretty wicked race condition in the precommit
scripts, namely writing to a directory that is outside of Jenkins' workspace
directory. I’ve committed changes this morning
[
https://issues.apache.org/jira/browse/HADOOP-11925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-11925.
---
Resolution: Fixed
Fix Version/s: 2.8.0
Thanks for the quick turn around
Allen Wittenauer created HADOOP-11925:
-
Summary: branch-2's smart-apply-patch.sh needs to be updated
Key: HADOOP-11925
URL: https://issues.apache.org/jira/browse/HADOOP-11925
Project: H
On May 5, 2015, at 11:05 AM, Rich Haase wrote:
> Can someone explain to me why on earth we care about limiting line length to
> 80 characters? Are there hadoop developers out there working from teletype
> terminals? Can we perhaps update this limit to something sane, like 120
> chars?
>
gt;> guarantees about files out of the main workspace.
>>
>> They all write to ${WORKSPACE}/../patchProcess, which will probably
>> collide
>> if multiple runs happen on the same machine. They also all blindly move
>> that directory at the end of the run.
>>
Allen Wittenauer created HADOOP-11917:
-
Summary: add patchprocess to .gitignore, rat checks; clean up
whitespace from pom.xml
Key: HADOOP-11917
URL: https://issues.apache.org/jira/browse/HADOOP-11917
Allen Wittenauer created HADOOP-11914:
-
Summary: test-patch.sh confused by certain patch formats
Key: HADOOP-11914
URL: https://issues.apache.org/jira/browse/HADOOP-11914
Project: Hadoop Common
So, as some may have noticed, I slammed the Jenkins servers over the
weekend to get some recent patch test runs in JIRA for the bug bash this week.
I've had a suspicion for a while now that either the long run times of the
hadoop-hdfs module unit tests (typically 2+ hours) or t
Allen Wittenauer created HADOOP-11909:
-
Summary: test-patch javac & javadoc output clarity
Key: HADOOP-11909
URL: https://issues.apache.org/jira/browse/HADOOP-11909
Project: Hadoop Co
Allen Wittenauer created HADOOP-11907:
-
Summary: update shell code to pass shellcheck 0.3.7
Key: HADOOP-11907
URL: https://issues.apache.org/jira/browse/HADOOP-11907
Project: Hadoop Common
Allen Wittenauer created HADOOP-11906:
-
Summary: test-patch.sh should use 'file' command for patch
determinism
Key: HADOOP-11906
URL: https://issues.apache.org/jira/browse/HADOOP-11906
Allen Wittenauer created HADOOP-11903:
-
Summary: test-patch should fail any new classes called Default-foo
Key: HADOOP-11903
URL: https://issues.apache.org/jira/browse/HADOOP-11903
Project: Hadoop
Allen Wittenauer created HADOOP-11897:
-
Summary: test-patch.sh plugins should abbreviate the path
Key: HADOOP-11897
URL: https://issues.apache.org/jira/browse/HADOOP-11897
Project: Hadoop Common
Hey gang.
With the commit of HADOOP-11866, the output for checkstyle and
whitespace has been greatly enhanced to actually be useful now. Instead of
getting weird output, you'll see the file, the line number and (in the case of
checkstyle) error. Note that line numbers are aft
Here’s the link in case you didn’t see it:
https://www.eventbrite.com/e/apache-hadoop-global-bug-bash-tickets-16507188445
Whether you are working virtually or in-person, it’s important for
everyone participating to register so that we can keep track of global
p
[
https://issues.apache.org/jira/browse/HADOOP-9572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-9572.
--
Resolution: Fixed
Closing this out as contained by HADOOP-11746 based upon the
Allen Wittenauer created HADOOP-11884:
-
Summary: test-patch.sh should pull the real findbugs version
Key: HADOOP-11884
URL: https://issues.apache.org/jira/browse/HADOOP-11884
Project: Hadoop
Allen Wittenauer created HADOOP-11882:
-
Summary: Audit all of the findbugs excludes
Key: HADOOP-11882
URL: https://issues.apache.org/jira/browse/HADOOP-11882
Project: Hadoop Common
Issue
Allen Wittenauer created HADOOP-11881:
-
Summary: test-patch.sh javac warning code is wildly wrong
Key: HADOOP-11881
URL: https://issues.apache.org/jira/browse/HADOOP-11881
Project: Hadoop Common
Allen Wittenauer created HADOOP-11880:
-
Summary: aw jira sub-task testing, ignore
Key: HADOOP-11880
URL: https://issues.apache.org/jira/browse/HADOOP-11880
Project: Hadoop Common
Issue
[
https://issues.apache.org/jira/browse/HADOOP-5628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-5628.
--
Resolution: Invalid
Closing this as stale.
test-patch.sh is now very smart about what
[
https://issues.apache.org/jira/browse/HADOOP-7790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-7790.
--
Resolution: Cannot Reproduce
Closing as stale.
> hadoop-yarn-api - generate-sour
[
https://issues.apache.org/jira/browse/HADOOP-7620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-7620.
--
Resolution: Won't Fix
Closing as won't fix. test-patch has been much be
[
https://issues.apache.org/jira/browse/HADOOP-7107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-7107.
--
Resolution: Implemented
Cancel+submit pair usually works. Closing as implemented
[
https://issues.apache.org/jira/browse/HADOOP-11320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-11320.
---
Resolution: Fixed
Based upon the previous discussion, it looks as though this
[
https://issues.apache.org/jira/browse/HADOOP-6282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-6282.
--
Resolution: Implemented
Closing as FindBugs is now implemented via maven. However it
[
https://issues.apache.org/jira/browse/HADOOP-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-6256.
--
Resolution: Won't Fix
HADOOP-11746 removed this code since it hasn't been in
[
https://issues.apache.org/jira/browse/HADOOP-7670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-7670.
--
Resolution: Implemented
This is pretty much what HADOOP-11746 does. Closing as
[
https://issues.apache.org/jira/browse/HADOOP-8483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-8483.
--
Resolution: Invalid
Closing as stale.
> test-patch +1 even there are build failu
[
https://issues.apache.org/jira/browse/HADOOP-6300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-6300.
--
Resolution: Won't Fix
A different method for dealing with warnings has
[
https://issues.apache.org/jira/browse/HADOOP-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-8344.
--
Resolution: Implemented
This has been implemented already. Closing.
> Improve t
[
https://issues.apache.org/jira/browse/HADOOP-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-8875.
--
Resolution: Implemented
> test-patch.sh doesn't test changes t
(Reply-to set to common-dev@)
With over 900 patches not yet reviewed and approved for Apache Hadoop,
it's time to make some strong progress on the bug list!
A number of Apache Hadoop committers and Hadoop-related tech companies
are hosting an Apache Hadoop Community event on Fri
On Apr 24, 2015, at 11:41 PM, Vinod Kumar Vavilapalli
wrote:
>
> Marco Zühlke pinged me offline informing me that I completely got my
> issue-count wrong.
>
> Seems like I had a very bizarre filter, I missed closing some tickets too at
> release time.
You were probably counting cha
On Apr 23, 2015, at 7:57 PM, Sidharta Seethana
wrote:
> About (3.) , a lot of the check style rules seem to be arcane/unnecessary.
> Please see : https://issues.apache.org/jira/browse/HADOOP-11869
a) I've closed it as a dupe of HADOOP-11866 to keep everything in one place.
b) I've had HADO
On Apr 24, 2015, at 3:09 AM, Brahma Reddy Battula
wrote:
> The patch artifact directory on has been removed!
> This is a fatal error for test-patch.sh. Aborting.
> Jenkins (node H8) information at
> https://builds.apache.org/job/PreCommit-YARN-Build/7477/ may provide some
> hints. ( did I mi
[
https://issues.apache.org/jira/browse/HADOOP-11869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-11869.
---
Resolution: Duplicate
Closing this as a dupe of HADOOP-11866.
> checkstyle ru
On Apr 22, 2015, at 11:34 PM, Zheng, Kai wrote:
> Hi Allen,
>
> This sounds great.
>
>>> Naming a patch foo-HDFS-7285.00.patch should get tested on the HDFS-7285
>>> branch.
> Does it happen locally in developer's machine when running test-patch.sh, or
> also mean something in Hadoop Jen
Oh, this is also in the release notes, but one can use a git reference # as
well. :) (with kudos to OOM for the idea.)
On Apr 22, 2015, at 8:57 PM, Allen Wittenauer wrote:
>
> More than likely. It probably needs more testing (esp under Jenkins).
>
> It should be noted that
Vavilapalli
wrote:
> Does this mean HADOOP-7435 is no longer needed / closeable as dup?
>
> Thanks
> +Vinod
>
> On Apr 22, 2015, at 12:34 PM, Allen Wittenauer wrote:
>
>>
>> Hey gang,
>>
>> Just so everyone is aware, if you are working on
Hey gang,
Just so everyone is aware, if you are working on a patch for either a
feature branch or a major branch, if you name the patch with the branch name
following the spec in HowToContribute (and a few other ways… test-patch tries
to figure it out!), test-patch.sh *should*
Err, first jira mentioned should be HADOOP-11861.
On Apr 22, 2015, at 8:10 AM, Allen Wittenauer wrote:
>
> Some status:
>
> * So far, HADOOP-11627 was filed which is luckily an extremely easy bug to
> fix.
>
> * There have been a few runs which seems to indicat
good news! The new mvn site test does appear to be capable of
catching issues! YARN-3410 was committed just prior to the new test code and
has markdown-to-html syntax issues. HADOOP-11627 (for example) shows the
results. :D
On Apr 21, 2015, at 10:48 PM, Allen Wittenauer wrote:
>
&g
FYI, MAPREDUCE-6324 is the first JIRA to be tested with the new code in place
if someone hasn’t seen the new output.
On Apr 21, 2015, at 9:06 PM, Allen Wittenauer wrote:
>
>
> Just a heads up that I’ll be committing this to trunk and branch-2 here
> in a bit. I’ll watch
16, 2015, at 7:38 PM, Chris Nauroth wrote:
> I'd like to thank Allen Wittenauer for his work on HADOOP-11746 to rewrite
> test-patch.sh. There is a lot of nice new functionality in there. My
> favorite part is that some patches will execute much faster, so I expect
> this will
[
https://issues.apache.org/jira/browse/HADOOP-11855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-11855.
---
Resolution: Duplicate
> Add -Djava.awt.headless=true to pom.xml entr
[
https://issues.apache.org/jira/browse/HADOOP-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer reopened HADOOP-10290:
---
JDK7 is not fixing this for me. Re-opening.
> Surefire steals focus on Ma
Allen Wittenauer created HADOOP-11855:
-
Summary: Add -Djava.awt.headless=true to pom.xml entries
Key: HADOOP-11855
URL: https://issues.apache.org/jira/browse/HADOOP-11855
Project: Hadoop Common
[
https://issues.apache.org/jira/browse/HADOOP-11845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-11845.
---
Resolution: Duplicate
I'm merging this into HADOOP-11746 so that the site
Allen Wittenauer created HADOOP-11845:
-
Summary: small bug in skipprnorep option handling in shelldocs.py
Key: HADOOP-11845
URL: https://issues.apache.org/jira/browse/HADOOP-11845
Project: Hadoop
Allen Wittenauer created HADOOP-11844:
-
Summary: SLS docs point to invalid rumen link
Key: HADOOP-11844
URL: https://issues.apache.org/jira/browse/HADOOP-11844
Project: Hadoop Common
Someone should look into HDFS-8132, which appears to have been filed against
RC0.
On Apr 11, 2015, at 1:44 AM, Vinod Kumar Vavilapalli wrote:
> Hi all,
>
> I've created a release candidate RC0 for Apache Hadoop 2.7.0.
>
> The RC is available at: http://people.apache.org/~vinodkv/hadoop-2.7.
[
https://issues.apache.org/jira/browse/HADOOP-11830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved HADOOP-11830.
---
Resolution: Invalid
Closing as invalid. Sqoop is not part of Hadoop
Allen Wittenauer created HADOOP-11820:
-
Summary: aw jira testing, ignore
Key: HADOOP-11820
URL: https://issues.apache.org/jira/browse/HADOOP-11820
Project: Hadoop Common
Issue Type: Task
. Let's go ahead and file a jira for
> it, unless others have objections.
>
> Chris Nauroth
> Hortonworks
> http://hortonworks.com/
>
>
>
>
>
>
> On 4/8/15, 8:32 AM, "Allen Wittenauer" wrote:
>
>>
>> Cancel the patch and it wo
Allen Wittenauer created HADOOP-11813:
-
Summary: releasedocmaker.py should use today's date instead of
unreleased
Key: HADOOP-11813
URL: https://issues.apache.org/jira/browse/HADOOP-11813
Pr
s much.
>>>
>>> I certainly have no objection to generating CHANGES.txt and release
>>> notes off JIRA, which avoids some of these problems (jiras can be
>>> edited, after all). But JIRA has its own set of problems... it's not
>>> always availab
Cancel the patch and it won’t do that.
Also, FWIW, HADOOP-11746 makes test-patch.sh run significantly faster for
non-Java patches. (of course, the current test-patch doesn’t publish times, so
it’s hard to know how slow it is. lol)
On Apr 8, 2015, at 12:39 AM, Gopal Vijayaraghavan wrote:
> H
601 - 700 of 1325 matches
Mail list logo
