+1 to auto-closing branch-1 issues.
-Sandy
On Fri, May 8, 2015 at 11:14 AM, Karthik Kambatla
wrote:
> Closing out the JIRAs as "Auto Closed" or "Closed due to Inactivity" seems
> reasonable to me. For branch-1, we can be more aggressive. We should
> probably do the same less aggressively for ot
My understanding was that the main reason that we labeled 2.0 alpha and 2.1
beta is that we wanted flexibility to make breaking API changes.
Is that the case now with 2.7? I.e. do we have APIs labeled as Public /
Stable that we want freedom to change in 2.8? If not, I definitely don't
think the
Hi Debashish,
Do you mind describing in a little more detail the benefits you're
interested in with different caching technology? The Hadoop distributed
cache, HDFS caching, memcached, and Hazelcast are all related to "caching",
but aim to solve very different problems.
-Sandy
On Mon, Oct 20, 2
If we've broken compatibility in branch-2, that's a bug that we need to
fix. HADOOP-10868 has not yet made it into a release; I don't see it as a
justification for solidifying the breakage.
-1 to upgrading Guava in branch-2.
On Tue, Sep 23, 2014 at 3:06 AM, Steve Loughran
wrote:
> +1 to upgradi
+1 (binding)
Ran a pseudo-distributed cluster with the Fair Scheduler and ran some
MapReduce example jobs.
-Sandy
On Wed, Sep 10, 2014 at 12:15 PM, Alejandro Abdelnur
wrote:
> Thanks Karthik.
>
> +1.
>
> + verified MD5 for source tarball
> + verified signature for source tarball
> + successful
I personally find Target Version to be useful for tracking which version a
change is intended for.
On Wed, Sep 3, 2014 at 2:55 PM, Karthik Kambatla wrote:
> On Tue, Sep 2, 2014 at 2:38 PM, Andrew Wang
> wrote:
>
> > Not to derail the conversation, but if CHANGES.txt is making backports
> more
+1 (binding)
On Fri, Aug 8, 2014 at 7:57 PM, Karthik Kambatla wrote:
> I have put together this proposal based on recent discussion on this topic.
>
> Please vote on the proposal. The vote runs for 7 days.
>
>1. Migrate from subversion to git for version control.
>2. Force-push to be di
+1 to going with git, and +1 to a rebase flow if we do so.
On Mon, Aug 4, 2014 at 10:43 AM, Andrew Purtell wrote:
> HBase recently made the leap from SVN to Git. Our early experience is
> positive, I think. My observations:
>
> When you commit a merge in git, the software will generate a merge
Thanks Arpit!
On Tue, Jul 29, 2014 at 2:24 PM, Arpit Agarwal
wrote:
> I cleared out the wiki page and left a forwarding link to the site docs.
> From a quick scan all the content is included in the site docs.
>
>
> On Tue, Jul 29, 2014 at 2:14 PM, Sandy Ryza
> wrote:
>
&
Eli pointed out to me that this is the up-to-date compatibility guide:
http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-common/Compatibility.html
Thanks,
Sandy
On Tue, Jul 29, 2014 at 9:39 AM, Sandy Ryza wrote:
> Hi Zhijie,
>
> The Hadoop compatibility guide mention
Hi Zhijie,
The Hadoop compatibility guide mentions this as "semantic compatibility":
http://wiki.apache.org/hadoop/Compatibility
My interpretation of the section is that we can't change the behavior of
public APIs unless we're fixing buggy behavior. If the change could break
an existing applicat
That policy makes sense to me. We should still label things @Private of
course so that it can be reflected in the documentation.
-Sandy
On Tue, Jul 22, 2014 at 2:54 PM, Karthik Kambatla
wrote:
> Hi devs
>
> As you might have noticed, we have several classes and methods in them that
> are not
While we haven't codified this in our compatibility guidelines, dropping a
Java version seems to me like change that needs to happen alongside a major
release. In plain talk, it has the ability to break everything for users
who aren't doing anything particularly unreasonable.
I don't think we sho
+1 (binding)
-Sandy
On Tue, Jun 24, 2014 at 7:53 AM, Devaraj K wrote:
> +1
>
> Thanks
> Devaraj K
>
>
> On Tue, Jun 24, 2014 at 2:23 PM, Arun C Murthy
> wrote:
>
> > Folks,
> >
> > As discussed, I'd like to call a vote on changing our by-laws to change
> > release votes from 7 days to 5.
> >
Hi WangYu and Debashish,
To unsubscribe from these mailing lists, send something to -
unsubscr...@hadoop.apache.org.
-Sandy
On Mon, Jun 23, 2014 at 7:23 PM, Maity, Debashish <
debashish.ma...@softwareag.com> wrote:
> Yes please do not send me communication again.
>
>
> -Original Message---
Andrew, correct me if I'm misunderstanding, but the incompatible change
that would require a major version bump is dropping support for JDK6.
On Mon, Jun 23, 2014 at 1:53 PM, sanjay Radia
wrote:
>
> On Jun 21, 2014, at 8:01 AM, Andrew Wang wrote:
>
> > This is why I'd like to keep my original
> > > > > > > > what it
>
> > > > took
>
> > > > > > > > to get them into a stable release. And at current course
>
> > > > > > > > and
>
> > > > speed,
>
> > > > > > >
Sandy Ryza created HADOOP-10688:
---
Summary: Expose thread-level FileSystem StatisticsData
Key: HADOOP-10688
URL: https://issues.apache.org/jira/browse/HADOOP-10688
Project: Hadoop Common
Issue
That sounds reasonable to me.
-Sandy
On Mon, Jun 9, 2014 at 9:39 AM, Arun C Murthy wrote:
> Folks,
>
> As you can see from the Roadmap wiki, it looks like several items are
> still a bit away from being ready.
>
> I think rather than wait for them, it will be useful to create an
> intermedia
to
point out that the proposal to merge AHS into trunk stated an intent to tie
ends up on security.
On Sun, Apr 13, 2014 at 7:50 PM, Sandy Ryza wrote:
> Unfortunately I don't have the bandwidth to take on ATS security at this
> time. My (I now understand mistaken) impression that i
if it
meant extending the target release date a couple weeks - I of course had no
intention to volunteer anybody for it.
On Sun, Apr 13, 2014 at 5:50 PM, Arun C Murthy wrote:
> Sandy,
>
> On Apr 12, 2014, at 10:09 AM, Sandy Ryza wrote:
>
> I'm having trouble editing the w
+1 for starting to think about 2.5. Early June seems a little early to me
- we had talked about a quarterly release cadence and this would be about
half that.
I'm having trouble editing the wiki, but I think Timeline Server stability
(e.g. security and locking down APIs) should go on that list.
It might make sense to try to enumerate the benefits of switching to Java7
APIs and dependencies. IMO, the ones listed so far on this thread don't
make a compelling enough case to drop Java6 in branch-2 on any time frame,
even if this means supporting Java6 through 2015. For example, the change
i
+1 for maintaining Java 6 support in branch-2.
Hadoop continuing to support Java 6 is not an endorsement of Java 6. It's
an acknowledgement that many users of Hadoop 2 have Java 6 embedded in
their stack, and that upgrading is costly for some users and simply not an
option for others. If a simil
block
> location file for scheduler is why i ask.
>
> -bc
>
>
> - Original Message -
> > From: "Sandy Ryza"
> > To: common-dev@hadoop.apache.org
> > Sent: Thursday, April 3, 2014 2:38:42 PM
> > Subject: Re: Yarn / mapreduce scheduling
> >
>
While the Scheduler Load Simulator isn't part of YARN's core, it's a tool
that YARN includes, and it's broken entirely in the current RC. YARN-1726
seems to me like something worth including in the release.
-Sandy
On Thu, Apr 3, 2014 at 11:12 AM, Xuan Gong wrote:
> +1 non-binding
>
> Built fr
The equivalent code in the Fair Scheduler is in AppSchedulable.java,
under assignContainer(FSSchedulerNode node, boolean reserved).
YARN uses delay scheduling (
http://people.csail.mit.edu/matei/papers/2010/eurosys_delay_scheduling.pdf)
for achieving data-locality.
-Sandy
On Thu, Apr 3, 2014 at
eline
> store is for storing per-framework data only, while we eventually hope to
> move the generic data there as well.
>
> Thanks,
> Zhijie
>
>
>
>
> On Mon, Mar 31, 2014 at 11:02 AM, Sandy Ryza >wrote:
>
> > What's the state of the application hist
What's the state of the application history server? Do we have security,
documentation, and are APIs stable? If any of these are missing, do we
have a plan for how to make this clear to users?
What about the timeline store?
thanks,
Sandy
On Mon, Mar 31, 2014 at 2:22 AM, Arun C Murthy wrote:
My understanding is that unfortunately we're stuck with these for the rest
of 2.x, because changing them could break jobs that rely on them. For jobs
that want to use newer versions, the recommendation is to use
mapreduce.user.classpath.first or turn on classpath isolation with
mapreduce.job.class
Looking forward to the release. What's the state of the application
history server? Do we have security, documentation, and are APIs stable?
If not, do we have a plan for how to make this clear to users?
What about the timeline store?
thanks,
Sandy
On Fri, Mar 14, 2014 at 8:23 PM, Arun C Mur
+1 (non-binding)
Built from source and ran jobs on a pseudo-distributed cluster with the
Fair Scheduler
On Wed, Feb 12, 2014 at 7:56 PM, Xuan Gong wrote:
> +1 (non-binding)
>
> downloaded the source tar ball, built, ran a number of MR jobs on a
> single-node cluster and checked the job history
+1 to reverting those JIRAs from branch-2.3. As YARN-1689 is fixing a
problem caused by YARN-1493 I think we can revert it in branch-2.3 as well.
I think we should leave them in branch-2 for now. We can revert if 2.4 is
imminent and they're holding it up, but hopefully the issues they caused
wil
I've been getting that too. Only on the Hadoop jira project though - YARN works
fine.
-Sandy
On Jan 30, 2014, at 12:44 AM, Steve Loughran wrote:
> On 30 January 2014 01:10, Masatake Iwasaki wrote:
>
>> Hi JIRA and Wiki admins,
>>
>> I would like permission to assign JIRA issues to myself
>>
It looks like Vinod just fixed this. Thanks!
On Tue, Jan 28, 2014 at 1:00 PM, Sandy Ryza wrote:
> I'm getting build errors on branch-2 because the pom for the new module
> still refers to 3.0.0-SNAPSHOT:
>
>
> hadoop-yarn-server
> org.apache.hado
found on the trunk, and to refactor the code about to
> share some pieces in PRC and web interfaces.
>
> *Release status*
>
>
> If the security stuff and the pending fixes arrive by the time
>
> everything
>
> else planned for Release 2.4 is done, we can include it as w
Going forward with commits because it seems like others have been doing so
On Mon, Jan 27, 2014 at 1:31 PM, Sandy Ryza wrote:
> We should hold off commits until that's done, right?
>
>
> On Mon, Jan 27, 2014 at 1:07 PM, Arun C Murthy wrote:
>
>> Yep, on it as
We should hold off commits until that's done, right?
On Mon, Jan 27, 2014 at 1:07 PM, Arun C Murthy wrote:
> Yep, on it as we speak. :)
>
>
> Arun
>
> On Jan 27, 2014, at 12:36 PM, Jason Lowe wrote:
>
> > Thanks, Arun. Are there plans to update the Fix Versions and
> CHANGES.txt accordingly?
[
https://issues.apache.org/jira/browse/HADOOP-10239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Ryza resolved HADOOP-10239.
-
Resolution: Fixed
Pushed this to the website
> Add Spark as a related project on the Had
+1 for a 2.4 (and 2.3) this month.
The current vote for YARN-321 is to merge it to trunk. Rereading the
discussion around YARN-321, my understanding is that it's unlikely to be
stable it by the end of the month. It still needs security and API
stabilization work. If we end up in a situation whe
hould merge into trunk only
> >
> > I would like to see #1 and #2 taken care before making a decision. The
> > reason for this is that if the source changes outside of the AHS are too
> > pervasive, then we may end up be making difficult backports from trunk to
> &
Very excited for this feature and appreciative of all the work put into
this. Reviewed the JIRA and my only two remaining concerns are about
documentation and API stability.
Regarding doc, while we don't necessarily need full documentation before
merging, my feeling is that we should at least hav
Re-reading the thread, it seems what I said about 2.2.1 never happening was
incorrect. My impression is still that nobody has plans to drive a 2.2.1
release on any particular timeline.
The changes that are now in 2.3 have been moved out of the branch-2.2.1. I
suppose the idea is that changes sla
Hi Santosh,
NodeManagers do not communicate with each other in YARN.
-Sandy
On Mon, Dec 9, 2013 at 5:42 PM, santosh kumar wrote:
> Hi,
>
> The communication in YARN is b/w RM-NM or AM-RM from what I know.
> Can Node Managers talk to each other? If so, how?
>
> Also what protocol or communicati
[
https://issues.apache.org/jira/browse/HADOOP-10145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Ryza resolved HADOOP-10145.
-
Resolution: Invalid
Please ask for assistance on the Hadoop user list. JIRA is for reporting
N-1333. Support blacklisting in the Fair Scheduler
YARN-1109. Demote NodeManager "Sending out status for container" logs
to debug (haosdent via Sandy Ryza)
YARN-1388. Fair Scheduler page always displays blank fair share
+1 to doing releases at some fixed time interval.
-Sandy
On W
Starting afresh with 2.2.1 and keeping it as small as possible sounds
reasonable to me.
Would love to get 2.3 out soon. To that end, how would people feel about
having code and/or feature freeze and/or ship dates? We've been way behind
out goals for recent releases. Having actual targets on the
Hi Amr,
The best place to start is searching for JIRAs with the "newbie" label.
Here are a couple YARN ones that I'd be happy to help you with:
https://issues.apache.org/jira/browse/YARN-1287
https://issues.apache.org/jira/browse/YARN-1109
https://issues.apache.org/jira/browse/YARN-1022
-Sandy
Thanks Steve. Just did the same for YARN. 7 JIRAs with 2.2.0 target
versions moved to 2.2.1.
-Sandy
On Fri, Oct 18, 2013 at 1:56 AM, Steve Loughran wrote:
> I've just moved the version 2.2.0 to the released category for
> HADOOP,COMMON and MAPREDUCE , ~6 JIRAs marked as fix for 2.2.0 went int
Thanks Eli, that explains it.
On Mon, Oct 14, 2013 at 3:30 PM, Eli Collins wrote:
> This is MAPREDUCE-4282
>
> On Mon, Oct 14, 2013 at 3:28 PM, Sandy Ryza
> wrote:
> > Doc existed in MR1 http://hadoop.apache.org/docs/stable/streaming.html,
> but
> > it looks like it
d file a jira for it. The
> wiki content here could be a good starting point.
>
> On Mon, Oct 14, 2013 at 2:56 PM, Sandy Ryza
> wrote:
> > Hi All,
> >
> > I noticed that the hadoop streaming documentation does not exist in the
> > Hadoop 2 source tree, and also
Hi All,
I noticed that the hadoop streaming documentation does not exist in the
Hadoop 2 source tree, and also cannot be found on the internet. Is this
on purpose? I found this wiki page
http://wiki.apache.org/hadoop/HadoopStreaming - is that where doc is
supposed to go? As this page isn't tie
+1 (non-binding)
Built from source and ran a few jobs on a pseudo-distributed cluster with
the Fair Scheduler.
On Tue, Oct 8, 2013 at 6:48 AM, Thomas Graves wrote:
> +1.
>
> Downloaded, verified signature/md5, CHANGES.txt, NOTICE, LICENSE, README,
> release notes, built the source tar ball, an
[
https://issues.apache.org/jira/browse/HADOOP-9775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Ryza resolved HADOOP-9775.
Resolution: Duplicate
> Add tracking IDs to FS tokens to allow tracing FS operations back to
rsh J wrote:
> Yes, but the heartbeat coupling isn't necessary I think. One could
> even use ZK write/watch approach for faster assignment of regular
> work?
>
> On Tue, Sep 24, 2013 at 2:24 PM, Steve Loughran
> wrote:
> > On 21 September 2013 09:19, Sandy Ryza wrote:
YARN-1089, which reforms CPU as a resource, is an incompatible change that
will need to go into 2.2.0. Should it go into 2.1.1-beta as well?
On Mon, Sep 23, 2013 at 11:42 AM, Andrew Wang wrote:
> We still need to resolve some symlink issues; are we planning to spin a new
> RC? Leaving it as-is
Hi All,
I just committed https://issues.apache.org/jira/browse/YARN-1128, which
fixes a severe Fair Scheduler bug, to branch-2.1-beta. 2.2.0 is the right
heading to put it under in CHANGES.txt, right?
Does anybody mind me adding a 2.2.0 version on JIRA?
thanks,
-Sandy
I don't believe there is any reason scheduling decisions need to be coupled
with NodeManager heartbeats. It doesn't sidestep any race conditions
because a NodeManager could die immediately after heartbeating.
On Sat, Sep 21, 2013 at 2:11 AM, Omkar Joshi wrote:
> Hi Wei,
>
> Yes there is a clea
+1 (non-binding)
Built from source, ran jobs on a pseudo-distributed cluster with the Fair
Scheduler.
-Sandy
On Tue, Aug 20, 2013 at 7:27 PM, Arun C Murthy wrote:
> Thanks for the heads up Aaron, I've changed fix-version of HDFS-4763 to
> 2.1.1-beta for now.
>
> Committers - please be careful
Vinod, your thinking makes sense to me. My two cents are that we should
hold off on fixes until 2.1.1-beta. Unless there are downstream projects
that need it to work for integration testing.
-Sandy
On Mon, Aug 19, 2013 at 2:49 PM, Vinod Kumar Vavilapalli wrote:
>
> Thanks for the clarificatio
How do we go about setting up builds on jdk7? Couldn't figure out how to
do it on Jenkins, so I'm assuming it either requires PMC or Infra?
-Sandy
On Thu, Jul 25, 2013 at 10:43 AM, Santhosh M S wrote:
> Resurrecting an old thread - now that JDK 6 is EOL should we switch over
> to JDK 7 across
Hi James,
In terms of areas of active development, there's still quite a bit to do in
MapReduce and YARN. ApplicationHistoryServer (YARN-321), Rolling Restart
(YARN-666), and work-preserving preemption are all in their early stages.
YARN in general could also still use some polish so there are pr
Sandy Ryza created HADOOP-9775:
--
Summary: Add tracking IDs to FS tokens to allow tracing FS
operations back to job
Key: HADOOP-9775
URL: https://issues.apache.org/jira/browse/HADOOP-9775
Project: Hadoop
tonworks Inc.* <http://www.hortonworks.com>
>
>
> On Fri, Jun 28, 2013 at 11:54 AM, Zhijie Shen
> wrote:
>
> > Have the same problem here, have to edit the patch manually to exclude
> the
> > changes in releasenotes.html
> >
> >
> > On Fri, Jun 28, 2013
Sandy Ryza created HADOOP-9675:
--
Summary: releasenotes.html always shows up as modified because of
line endings issues
Key: HADOOP-9675
URL: https://issues.apache.org/jira/browse/HADOOP-9675
Project
For YARN-791, if we can come to consensus on the correct approach, I can
try to have a patch ASAP.
-Sandy
On Fri, 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
Has anybody else been having trouble with line endings since pulling trunk
recently?
hadoop-common-project/hadoop-common/src/main/docs/releasenotes.html
shows up as modified even though I haven't touched it, and I can't check it
out or reset to a previous version to make that go away. The only th
Sandy Ryza created HADOOP-9672:
--
Summary: Upgrade Avro dependency
Key: HADOOP-9672
URL: https://issues.apache.org/jira/browse/HADOOP-9672
Project: Hadoop Common
Issue Type: Improvement
Sandy Ryza created HADOOP-9661:
--
Summary: Allow metrics sources to be extended
Key: HADOOP-9661
URL: https://issues.apache.org/jira/browse/HADOOP-9661
Project: Hadoop Common
Issue Type
+1 (non-binding)
Built from source, ran a few sample jobs on a pseudo-distributed cluster
On Mon, Jun 3, 2013 at 3:22 PM, Chris Douglas wrote:
> +1
>
> Checksum and signature match, ran some unit tests, checked diff
> against 2.0.4-alpha.
>
> Thanks for seeing this through, Cos. -C
>
> On Mon,
+1 (non-binding). Did a full build from source and ran a few sample jobs
on a pseudo-distributed cluster.
-Sandy
On Mon, Jun 3, 2013 at 11:29 AM, Kihwal Lee wrote:
> +1 I've downloaded & built the RC and ran several tests on a single node
> cluster.
>
> Kihwal
>
> On 5/28/13 11:00 AM, "Thomas
+1 (non-binding)
On Tue, May 21, 2013 at 4:02 PM, Eli Collins wrote:
> +1 thanks Matt.
>
>
> On Tue, May 21, 2013 at 2:10 PM, Matt Foley wrote:
>
> > Hi all,
> > This has been a side topic in several email threads recently. Currently
> we
> > have an ambiguity. We have a tradition in the de
+1 (non-binding)
On Sun, May 19, 2013 at 1:22 PM, Derek Dagit wrote:
> +1 (non-binding)
>
> On May 17, 2013, at 4:14 PM, "Thomas Graves"
> wrote:
>
> > Hello all,
> >
> > We've had a few critical issues come up in 0.23.7 that I think warrants a
> > 0.23.8 release. The main one is MAPREDUCE-521
+1 (non-binding)
Agreed with Bikas that we should get the scheduler API enhancements
(YARN-397) in we are able, but they don't need to be blockers because they
will be backwards compatible.
Arun, not sure whether your "Yes to all" already covered this, but I'd like
to throw in support for the com
Hi Amr,
Hadoop contains the FIFO scheduler and two more advanced schedulers, the
capacity scheduler, developed at Yahoo, and the fair scheduler, developed
at Facebook.
In Hadoop 2, the fair scheduler code is located in
the org.apache.hadoop.yarn.server.resourcemanager.scheduler.fair package,
and
+1 (non-binding)
Built from source and ran a couple of MR examples on a single node cluster.
-Sandy
On Wed, Apr 17, 2013 at 12:03 PM, Siddharth Seth
wrote:
> +1 (binding).
> Verified checksums and signature.
> Built from source tar, deployed a single node cluster (CapacityScheduler)
> and tried
+1 (non-binding)
Built from source and ran sample jobs concurrently with the fair scheduler
on a single node cluster.
On Fri, Apr 12, 2013 at 2:56 PM, Arun C Murthy wrote:
> Folks,
>
> I've created a release candidate (RC2) for hadoop-2.0.4-alpha that I would
> like to release.
>
> The RC is a
; Fax# 512-838-8858
>
>
>
> [image: Inactive hide details for Sandy Ryza ---04/08/2013 02:17:42
> PM---Hi Amir, Yeah, there is. Under the "More Actions" menu, there]Sandy
> Ryza ---04/08/2013 02:17:42 PM---Hi Amir, Yeah, there is. Under the "More
> Actions&q
Hi Amir,
Yeah, there is. Under the "More Actions" menu, there's a "Move" option,
which allows you to transfer the JIRA to another project.
-Sandy
On Mon, Apr 8, 2013 at 12:09 PM, Amir Sanjar wrote:
> Hi is there a way to transfer a HADOOP jira to a MAPREDUCE jira?
>
> Best Regards
> Amir Sanj
Yeah, this was fixed by YARN-377
-Sandy
On Wed, Apr 3, 2013 at 4:15 PM, Amir Sanjar wrote:
>
> Has anyone seen below failure?
>
> Unit test case Name : TestContainersMonitor
> Hadoop Vesrion : Hadoop-2.0.3.
> Java Version : java version "1.6.0" sr12 & ORACLE JAVA
> platform : RHEL 6.x, x86_64
Sandy Ryza created HADOOP-9300:
--
Summary: Streaming fails to set output key class when reducer is
java class
Key: HADOOP-9300
URL: https://issues.apache.org/jira/browse/HADOOP-9300
Project: Hadoop
Sandy Ryza created HADOOP-9178:
--
Summary: etc/hadoop is missing hadoop-env.sh
Key: HADOOP-9178
URL: https://issues.apache.org/jira/browse/HADOOP-9178
Project: Hadoop Common
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HADOOP-9141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandy Ryza resolved HADOOP-9141.
Resolution: Duplicate
Duplicate of HADOOP-9153. My bad.
> Add support
Sandy Ryza created HADOOP-9153:
--
Summary: Support createNonRecursive in ViewFileSystem
Key: HADOOP-9153
URL: https://issues.apache.org/jira/browse/HADOOP-9153
Project: Hadoop Common
Issue Type
Sandy Ryza created HADOOP-9141:
--
Summary: Add support for createNonRecursive to ViewFileSystem
Key: HADOOP-9141
URL: https://issues.apache.org/jira/browse/HADOOP-9141
Project: Hadoop Common
Sandy Ryza created HADOOP-8969:
--
Summary: In TestIFile, testIFileReaderWithCodec relies on
testIFileWriterWithCodec
Key: HADOOP-8969
URL: https://issues.apache.org/jira/browse/HADOOP-8969
Project
Sandy Ryza created HADOOP-8913:
--
Summary: hadoop-metrics2.properties should give units in comment
for sampling period
Key: HADOOP-8913
URL: https://issues.apache.org/jira/browse/HADOOP-8913
Project
Sandy Ryza created HADOOP-8775:
--
Summary: MR2 distcp permits non-positive value to -bandwidth
option which causes job never to complete
Key: HADOOP-8775
URL: https://issues.apache.org/jira/browse/HADOOP-8775
88 matches
Mail list logo
