[
https://issues.apache.org/jira/browse/HADOOP-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HADOOP-1216:
--
Status: Open (was: Patch Available)
Runping, as of HADOOP-1127 the PhasedFileSystem is deprec
[
https://issues.apache.org/jira/browse/HADOOP-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491870
]
eric baldeschwieler commented on HADOOP-1296:
-
So are we comfortable returning 100s of thousands of reco
[
https://issues.apache.org/jira/browse/HADOOP-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491859
]
Hadoop QA commented on HADOOP-1216:
---
+1
http://issues.apache.org/jira/secure/attachment/12356289/patch_1216.txt a
[
https://issues.apache.org/jira/browse/HADOOP-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-1216:
---
Status: Patch Available (was: Open)
> Hadoop should support reduce none option
> --
[
https://issues.apache.org/jira/browse/HADOOP-1216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-1216:
---
Attachment: patch_1216.txt
This patch implements the feature of setting numReduceTasks=0.
In that c
[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491854
]
Kurtis Heimerl commented on HADOOP-1298:
Fixed the patch, now has user.java.
I am aware of the performance
[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurtis Heimerl updated HADOOP-1298:
---
Attachment: hadoop-user-munncha.patch
this one has User.java
> adding user info to file
> -
[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491851
]
Raghu Angadi commented on HADOOP-1298:
--
The patch not include User.java.
Anything you add to each INode is goi
The current state of things is included in the patch associated with this
ticket.
Right now the user and group info is read from config. I was hoping for some
feedback as to this design for the next iteration.
Thanks.
On 4/25/07, Kurtis Heimerl (JIRA) <[EMAIL PROTECTED]> wrote:
adding user in
[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurtis Heimerl updated HADOOP-1298:
---
Attachment: hadoop-user-munncha.patch
Here's the current state of the work.
> adding user
adding user info to file
Key: HADOOP-1298
URL: https://issues.apache.org/jira/browse/HADOOP-1298
Project: Hadoop
Issue Type: New Feature
Components: dfs, fs
Reporter: Kurtis Heimerl
I'm workin
[
https://issues.apache.org/jira/browse/HADOOP-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491839
]
Hairong Kuang commented on HADOOP-1263:
---
The annotation method proposed in HADOOP-601 to provide a general ret
[
https://issues.apache.org/jira/browse/HADOOP-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491819
]
Hadoop QA commented on HADOOP-1297:
---
+1
http://issues.apache.org/jira/secure/attachment/12356274/datanodeDeleteBl
[
https://issues.apache.org/jira/browse/HADOOP-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491810
]
Doug Cutting commented on HADOOP-1295:
--
bq. Can it only run this code if HADOOP_HOME is not already set?
That
[
https://issues.apache.org/jira/browse/HADOOP-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1184:
-
Attachment: decommissionOneReplica4.patch
Incorporated Hairong's review comments.
> Dec
[
https://issues.apache.org/jira/browse/HADOOP-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491806
]
Raghu Angadi commented on HADOOP-1202:
--
bq. ... I need to talk to my namenode to retrieve the results of my job
[
https://issues.apache.org/jira/browse/HADOOP-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491804
]
Lee Faris commented on HADOOP-1295:
---
Yes I get it. We need to find the hadoop root. Is there a way to just pass
[
https://issues.apache.org/jira/browse/HADOOP-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1297:
-
Status: Patch Available (was: Open)
> datanode sending block reports to namenode once e
[
https://issues.apache.org/jira/browse/HADOOP-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1297:
-
Attachment: datanodeDeleteBlocks2.patch
Inserted comment saying that the f.exists() that
[
https://issues.apache.org/jira/browse/HADOOP-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491800
]
Michael Bieniosek commented on HADOOP-785:
--
Has anybody done any work on this issue? This seems like an imp
[
https://issues.apache.org/jira/browse/HADOOP-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1297:
-
Attachment: (was: datanodeDeleteBlocks.patch)
> datanode sending block reports to na
[
https://issues.apache.org/jira/browse/HADOOP-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491797
]
Raghu Angadi commented on HADOOP-1297:
--
+1.
Couple of minor things:
# {{invalidBlks[i] + "file "}} neess a sp
[
https://issues.apache.org/jira/browse/HADOOP-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Bieniosek updated HADOOP-1202:
--
Description:
There is no way to tell the jobtracker & namenode to listen on more than
[
https://issues.apache.org/jira/browse/HADOOP-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491792
]
Hairong Kuang commented on HADOOP-1263:
---
On a second thought, I feel that simply adding a retry mechanism to i
[
https://issues.apache.org/jira/browse/HADOOP-1297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1297:
-
Attachment: datanodeDeleteBlocks.patch
> datanode sending block reports to namenode once
[
https://issues.apache.org/jira/browse/HADOOP-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491783
]
Hadoop QA commented on HADOOP-1293:
---
+1
http://issues.apache.org/jira/secure/attachment/12356262/1293.patch appli
datanode sending block reports to namenode once every second
Key: HADOOP-1297
URL: https://issues.apache.org/jira/browse/HADOOP-1297
Project: Hadoop
Issue Type: Bug
Compo
[
https://issues.apache.org/jira/browse/HADOOP-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491779
]
Owen O'Malley commented on HADOOP-1296:
---
> Another question, does getFileHints still need the parameters "star
[
https://issues.apache.org/jira/browse/HADOOP-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491776
]
Owen O'Malley commented on HADOOP-1296:
---
Maybe I was just trying to be too clever. :)
Since the BlockInfo's c
[
https://issues.apache.org/jira/browse/HADOOP-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491775
]
Raghu Angadi commented on HADOOP-1220:
--
It at least confirms to us if f.delete() is indeed the problem or not.
[
https://issues.apache.org/jira/browse/HADOOP-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491774
]
Doug Cutting commented on HADOOP-1270:
--
This looks reasonable to me. Have you yet tested whether it improves
[
https://issues.apache.org/jira/browse/HADOOP-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491772
]
dhruba borthakur commented on HADOOP-1220:
--
I am not too inclined to put in a check to f.exists() after eve
[
https://issues.apache.org/jira/browse/HADOOP-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491769
]
Doug Cutting commented on HADOOP-1295:
--
I think this is for when someone makes a link to bin/hadoop in, e.g., ~
[
https://issues.apache.org/jira/browse/HADOOP-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491766
]
Raghu Angadi commented on HADOOP-1220:
--
> The failure to delete the fail seems [...]
should be: .. delete the F
[
https://issues.apache.org/jira/browse/HADOOP-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491765
]
Raghu Angadi commented on HADOOP-1220:
--
The failure to delete the fail seems to happen when a lot of blocks ar
[
https://issues.apache.org/jira/browse/HADOOP-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1220:
-
Attachment: datanodeDeleteBlocks.patch
Implemented the changes described in the previous
[
https://issues.apache.org/jira/browse/HADOOP-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur reassigned HADOOP-1220:
Assignee: dhruba borthakur
> block not found in blockMap
> ---
[
https://issues.apache.org/jira/browse/HADOOP-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Noguchi updated HADOOP-1293:
-
Status: Patch Available (was: Open)
> stderr from streaming skipped after first 20 lines.
> -
[
https://issues.apache.org/jira/browse/HADOOP-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491762
]
Hairong Kuang commented on HADOOP-1296:
---
I feel that we need either getStart() or getSize(). It seems that get
[
https://issues.apache.org/jira/browse/HADOOP-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491761
]
Koji Noguchi commented on HADOOP-1220:
--
bq. This time the block in question does not appear in the dfs data dir
[
https://issues.apache.org/jira/browse/HADOOP-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491757
]
Jeremy commented on HADOOP-1202:
I agree that there are some configuration issues here that need to be addressed.
I
Wonderful!
On Apr 25, 2007, at 12:30 PM, Runping Qi wrote:
Arkady,
The FieldSelectionMapReduce class and KeyFieldBasedPartitioner class
allows
to do exactly what you want (namely, you select fields 6,3,8 and 5 as
your
sorting keys).
Runping
-Original Message-
From: Arkady Bork
[
https://issues.apache.org/jira/browse/HADOOP-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491756
]
Runping Qi commented on HADOOP-1293:
+1
This looks goo.
> stderr from streaming skipped after first 20 lines
[
https://issues.apache.org/jira/browse/HADOOP-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491751
]
Hadoop QA commented on HADOOP-1176:
---
+1
http://issues.apache.org/jira/secure/attachment/12356182/HADOOP-1176_2007
[
https://issues.apache.org/jira/browse/HADOOP-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491747
]
Doug Cutting commented on HADOOP-435:
-
bq. Once this gets committed I would be happy to open the issue to patch
[
https://issues.apache.org/jira/browse/HADOOP-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491743
]
Hadoop QA commented on HADOOP-1279:
---
+1
http://issues.apache.org/jira/secure/attachment/12355916/HADOOP-1279_2007
Runping,
as we discussed yesterday, it may be better to implement more complete
functionality that would allow to specify any combination of fields to
be used as for partitioning and for sorting.
This can be easily implemented top of the functionality this specific
patch provides. (By prep
[
https://issues.apache.org/jira/browse/HADOOP-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HADOOP-1176:
--
Status: Patch Available (was: Open)
Thanks to Hairong for helping test it...
> Reduce hang o
[
https://issues.apache.org/jira/browse/HADOOP-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HADOOP-1279:
--
Fix Version/s: 0.13.0
Status: Patch Available (was: Open)
Thanks to Alejandro for
[
https://issues.apache.org/jira/browse/HADOOP-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491742
]
Arun C Murthy commented on HADOOP-1279:
---
Arkady, all information is persisted already into 'JobTracker History
[
https://issues.apache.org/jira/browse/HADOOP-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491735
]
dhruba borthakur commented on HADOOP-1296:
--
Do we need BlockInfo to expose a getSize() method? It will retu
[
https://issues.apache.org/jira/browse/HADOOP-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491739
]
arkady borkovsky commented on HADOOP-1279:
--
It would be very nice if the information about completed jobs i
[
https://issues.apache.org/jira/browse/HADOOP-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491733
]
Owen O'Malley commented on HADOOP-1296:
---
No, this is in FileSystem not DFS. There are no classes that are rele
Arkady,
The FieldSelectionMapReduce class and KeyFieldBasedPartitioner class allows
to do exactly what you want (namely, you select fields 6,3,8 and 5 as your
sorting keys).
Runping
> -Original Message-
> From: Arkady Borkovsky [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 25, 2007
[
https://issues.apache.org/jira/browse/HADOOP-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491731
]
Konstantin Shvachko commented on HADOOP-1296:
-
BlockInfo is reserved.
We may use LocatedBlock class inst
[
https://issues.apache.org/jira/browse/HADOOP-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491730
]
Hairong Kuang commented on HADOOP-1263:
---
Tome, thank you so much. Owen also mentioned the retry package to me
[
https://issues.apache.org/jira/browse/HADOOP-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491728
]
arkady borkovsky commented on HADOOP-1296:
--
Can this be extended to support wild cards (or rather all files
[
https://issues.apache.org/jira/browse/HADOOP-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491727
]
dhruba borthakur commented on HADOOP-1220:
--
This problem occured again. This time the block in question doe
[
https://issues.apache.org/jira/browse/HADOOP-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491726
]
Hairong Kuang commented on HADOOP-1176:
---
+1 patch 5 works.
> Reduce hang on huge map output
> ---
Improve interface to FileSystem.getFileCacheHints
-
Key: HADOOP-1296
URL: https://issues.apache.org/jira/browse/HADOOP-1296
Project: Hadoop
Issue Type: Improvement
Components: fs
[
https://issues.apache.org/jira/browse/HADOOP-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-1284:
---
Status: Patch Available (was: Open)
> clean up the protocol between stream mapper/reducer and the f
[
https://issues.apache.org/jira/browse/HADOOP-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-1284:
---
Attachment: patch-1284.txt
> clean up the protocol between stream mapper/reducer and the framework
>
[
https://issues.apache.org/jira/browse/HADOOP-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-1284:
---
Description:
Right now, the protocol between stream mapper/reducer and the framework is very
inflex
[
https://issues.apache.org/jira/browse/HADOOP-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491725
]
Hadoop QA commented on HADOOP-1284:
---
+1
http://issues.apache.org/jira/secure/attachment/12356261/patch-1284.txt a
[
https://issues.apache.org/jira/browse/HADOOP-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491719
]
Runping Qi commented on HADOOP-1290:
Ooops, wrong JARA.
> Move Hadoop Abacus to hadoop.mapred.lib
> -
[
https://issues.apache.org/jira/browse/HADOOP-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Noguchi updated HADOOP-1293:
-
Attachment: 1293.patch
1) Took out logprintln(lineStr);
2) Always System.err.println(lineStr);
[
https://issues.apache.org/jira/browse/HADOOP-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-1290:
---
Attachment: patch-1284.txt
This patch implemented the proposed protocol.
With this patch, the stre
[
https://issues.apache.org/jira/browse/HADOOP-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-1290:
---
Attachment: (was: patch-1284.txt)
> Move Hadoop Abacus to hadoop.mapred.lib
> --
[
https://issues.apache.org/jira/browse/HADOOP-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Noguchi reassigned HADOOP-1293:
Assignee: Koji Noguchi
> stderr from streaming skipped after first 20 lines.
> -
hadoop-config.sh resolving symlinks leads to errors
Key: HADOOP-1295
URL: https://issues.apache.org/jira/browse/HADOOP-1295
Project: Hadoop
Issue Type: Improvement
Components: s
[
https://issues.apache.org/jira/browse/HADOOP-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lee Faris updated HADOOP-1295:
--
Priority: Minor (was: Major)
> hadoop-config.sh resolving symlinks leads to errors
> ---
[
https://issues.apache.org/jira/browse/HADOOP-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491694
]
Hadoop QA commented on HADOOP-485:
--
+1
http://issues.apache.org/jira/secure/attachment/12356251/485.patch applied a
[
https://issues.apache.org/jira/browse/HADOOP-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tahir Hashmi updated HADOOP-485:
Status: Patch Available (was: Open)
> allow a different comparator for grouping keys in calls to r
[
https://issues.apache.org/jira/browse/HADOOP-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tahir Hashmi updated HADOOP-485:
Attachment: 485.patch
This patch addresses Devaraj's comments. I could run the specific unit test f
[
https://issues.apache.org/jira/browse/HADOOP-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491659
]
Benjamin Reed commented on HADOOP-435:
--
Unjaring is gratuitous and annoying. There are environments, such as our
[
https://issues.apache.org/jira/browse/HADOOP-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devaraj Das updated HADOOP-1252:
Attachment: 1252.patch
Adopted a simple strategy for this:
Basically, the strategy is to do round-
[
https://issues.apache.org/jira/browse/HADOOP-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491632
]
Hadoop QA commented on HADOOP-1294:
---
+1
http://issues.apache.org/jira/secure/attachment/12356233/java6_unchecked.
It looks like there may be two problems here. The first is a result of
HADOOP-1190, see https://issues.apache.org/jira/browse/HADOOP-1294 for
the fix. The second looks like it's to do with picking up the correct
hostname, which is probably unrelated to the fixes in HADOOP-1190.
Have you made any o
[
https://issues.apache.org/jira/browse/HADOOP-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-1294:
--
Status: Patch Available (was: In Progress)
> Fix unchecked warnings in main Hadoop code under Java 6.
[
https://issues.apache.org/jira/browse/HADOOP-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HADOOP-1294 started by Tom White.
> Fix unchecked warnings in main Hadoop code under Java 6.
>
>
>
[
https://issues.apache.org/jira/browse/HADOOP-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HADOOP-1294:
--
Attachment: java6_unchecked.patch
This is occurring because the getConstructor method on Class changed
Fix unchecked warnings in main Hadoop code under Java 6.
Key: HADOOP-1294
URL: https://issues.apache.org/jira/browse/HADOOP-1294
Project: Hadoop
Issue Type: Bug
Components: t
[
https://issues.apache.org/jira/browse/HADOOP-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HADOOP-1270:
--
Attachment: HADOOP-1270_20070425_1.patch
Here is a straight-forward patch which randomizes the
[
https://issues.apache.org/jira/browse/HADOOP-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy reassigned HADOOP-1270:
-
Assignee: Arun C Murthy
> Randomize the fetch of map outputs
> -
Also found the following in the test's log:
- ---
- Standard Error -
Waiting for the Mini HDFS Cluster to start...
- ---
Testcase: testCheckpoint took 3.783 sec
Caused an ERROR
Hi!
I've started getting lots of failures in DFS unit tests since updating
to trunk revision 532317. I get the following warning while building:
[javac]
/home/tahir/Desktop/Trunk/trunk/src/test/org/apache/hadoop/dfs/ClusterTestDFS.java:439:
warning: [unchecked] unchecked call to
getCons
[
https://issues.apache.org/jira/browse/HADOOP-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491609
]
Hadoop QA commented on HADOOP-1190:
---
Integrated in Hadoop-Nightly #69 (See
http://lucene.zones.apache.org:8080/hu
[
https://issues.apache.org/jira/browse/HADOOP-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491608
]
Hadoop QA commented on HADOOP-1282:
---
Integrated in Hadoop-Nightly #69 (See
http://lucene.zones.apache.org:8080/hu
[
https://issues.apache.org/jira/browse/HADOOP-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491561
]
Tom White commented on HADOOP-435:
--
I like what this patch does, but I think the reluctance to commit it might stem
[
https://issues.apache.org/jira/browse/HADOOP-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491553
]
Tom White commented on HADOOP-1263:
---
We should be able to use the org.apache.hadoop.io.retry package for this. See
[
https://issues.apache.org/jira/browse/HADOOP-1279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491544
]
Alejandro Abdelnur commented on HADOOP-1279:
+1
tested the patch and it fixes the issue.
thxs.
> lis
[
https://issues.apache.org/jira/browse/HADOOP-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491541
]
Hadoop QA commented on HADOOP-1272:
---
+1
http://issues.apache.org/jira/secure/attachment/12356205/innerclasses4.pa
[
https://issues.apache.org/jira/browse/HADOOP-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1272:
-
Status: Patch Available (was: Open)
> Extract InnerClasses from FSNamesystem into separ
[
https://issues.apache.org/jira/browse/HADOOP-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1272:
-
Attachment: (was: innerclasses3.patch)
> Extract InnerClasses from FSNamesystem into
[
https://issues.apache.org/jira/browse/HADOOP-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1272:
-
Attachment: innerclasses4.patch
Hi Konstantin, thanks for the feedback. I agree that mov
95 matches
Mail list logo
