[
https://issues.apache.org/jira/browse/HADOOP-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525894
]
eric baldeschwieler commented on HADOOP-1700:
-
Yes, I'd thought of using length too. We have had reques
I think we should also add an available RAM variable and then do a
reasonable job of deriving a bunch of the other variables in these
settings from that (we may need one for task trackers, one for
namenodes and so on.
A lot of the memory related default settings make no sense on the
boxes
[
https://issues.apache.org/jira/browse/HADOOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman updated HADOOP-1801:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Tests passed. Committed.
>
[
https://issues.apache.org/jira/browse/HADOOP-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman updated HADOOP-1847:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Tests passed. Committed.
>
[
https://issues.apache.org/jira/browse/HADOOP-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525883
]
Hadoop QA commented on HADOOP-1266:
---
+1
http://issues.apache.org/jira/secure/attachment/12365303/GenericTopology.
[
https://issues.apache.org/jira/browse/HADOOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525879
]
Hadoop QA commented on HADOOP-1801:
---
+1
http://issues.apache.org/jira/secure/attachment/12365380/HADOOP-1801-patc
[
https://issues.apache.org/jira/browse/HADOOP-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525874
]
Rafael Turk commented on HADOOP-1793:
-
Not any more...
> [hbase] Remove deprecated HClient class
>
Support for big jar file (>2G)
--
Key: HADOOP-1864
URL: https://issues.apache.org/jira/browse/HADOOP-1864
Project: Hadoop
Issue Type: Bug
Components: contrib/streaming
Reporter: Yiping Han
[
https://issues.apache.org/jira/browse/HADOOP-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525872
]
Raghu Angadi commented on HADOOP-1859:
--
BufferedInputStream.available() throws an IOException (this is closest
[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525871
]
Christophe Taton commented on HADOOP-1298:
--
This list sounds about right to my mind also. I think we can po
[
https://issues.apache.org/jira/browse/HADOOP-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525868
]
Hadoop QA commented on HADOOP-1847:
---
+1
http://issues.apache.org/jira/secure/attachment/12365367/patch.txt applie
[
https://issues.apache.org/jira/browse/HADOOP-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525866
]
Doug Cutting commented on HADOOP-1859:
--
> I think it should throw an IOException.
Hmm. Maybe. I think runtim
[
https://issues.apache.org/jira/browse/HADOOP-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525865
]
Raghu Angadi commented on HADOOP-1298:
--
Christophe, everyone is eager to get this into 0.15. Lets list TODOs at
[
https://issues.apache.org/jira/browse/HADOOP-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525860
]
irubin edited comment on HADOOP-1828 at 9/7/07 4:05 PM:
-
Hi there,
I'm attaching a new
[
https://issues.apache.org/jira/browse/HADOOP-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525863
]
Raghu Angadi commented on HADOOP-1859:
--
I think it should throw an IOException.
> FSInputDataStream.getPos thr
[
https://issues.apache.org/jira/browse/HADOOP-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated HADOOP-1853:
-
Resolution: Invalid
Status: Resolved (was: Patch Available)
I just committed this. Tha
[
https://issues.apache.org/jira/browse/HADOOP-1828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Izaak Rubin updated HADOOP-1828:
Attachment: shell_2.patch
Hi there,
I'm attaching a new patch (shell_2.patch) which is a cleaned-
[
https://issues.apache.org/jira/browse/HADOOP-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525858
]
Hadoop QA commented on HADOOP-120:
--
+1
http://issues.apache.org/jira/secure/attachment/12365371/hadoop-120-workarou
[
https://issues.apache.org/jira/browse/HADOOP-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525852
]
Hairong Kuang commented on HADOOP-1846:
---
I plan to fix the problem by changing the datanodeReport protocol to
[
https://issues.apache.org/jira/browse/HADOOP-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hairong Kuang updated HADOOP-1266:
--
Fix Version/s: 0.15.0
Affects Version/s: 0.14.1
Status: Patch Available
[
https://issues.apache.org/jira/browse/HADOOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman updated HADOOP-1801:
--
Status: Patch Available (was: Open)
Only run one HRegionServer. This *should* fix the problem
[
https://issues.apache.org/jira/browse/HADOOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman updated HADOOP-1801:
--
Attachment: HADOOP-1801-patch.txt
> [hbase] When hdfs is yanked out from under hbase, hbase sh
[
https://issues.apache.org/jira/browse/HADOOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman updated HADOOP-1801:
--
Status: Open (was: Patch Available)
Fix patch. Locks up on Hudson.
> [hbase] When hdfs is ya
[
https://issues.apache.org/jira/browse/HADOOP-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525849
]
dhruba borthakur commented on HADOOP-1861:
--
4. Configuration for including and excluding specific nodes fro
add a batch option to pipes launcher
Key: HADOOP-1863
URL: https://issues.apache.org/jira/browse/HADOOP-1863
Project: Hadoop
Issue Type: New Feature
Components: pipes
Affects Versions: 0.14.
[
https://issues.apache.org/jira/browse/HADOOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525846
]
Hadoop QA commented on HADOOP-1801:
---
-1, build or testing failed
2 attempts failed to build and test the latest a
reduces are getting stuck trying to find map outputs
Key: HADOOP-1862
URL: https://issues.apache.org/jira/browse/HADOOP-1862
Project: Hadoop
Issue Type: Bug
Components: mapred
[
https://issues.apache.org/jira/browse/HADOOP-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HADOOP-1351:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Than
[
https://issues.apache.org/jira/browse/HADOOP-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525834
]
Doug Cutting commented on HADOOP-785:
-
I prefer calling these parameters "final" rather than "force". The "final
[
https://issues.apache.org/jira/browse/HADOOP-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525829
]
Hadoop QA commented on HADOOP-1819:
---
+1
http://issues.apache.org/jira/secure/attachment/12365368/jt-init-2.patch
[
https://issues.apache.org/jira/browse/HADOOP-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated HADOOP-1687:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thank
[
https://issues.apache.org/jira/browse/HADOOP-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525822
]
Doug Cutting commented on HADOOP-1859:
--
What should it do? I always thought it was an error to call any method
[
https://issues.apache.org/jira/browse/HADOOP-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-1833:
--
Resolution: Fixed
Fix Version/s: 0.15.0
Status: Resolved (was: Patch Available)
Committed.
[
https://issues.apache.org/jira/browse/HADOOP-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525816
]
Arun C Murthy commented on HADOOP-1351:
---
+1 (finally! *smile*)
Thanks for your patience on this one Enis!
> W
[
https://issues.apache.org/jira/browse/HADOOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman updated HADOOP-1801:
--
Fix Version/s: 0.15.0
Affects Version/s: 0.15.0
Status: Patch Available
[
https://issues.apache.org/jira/browse/HADOOP-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman updated HADOOP-1801:
--
Attachment: HADOOP-1801-patch.txt
> [hbase] When hdfs is yanked out from under hbase, hbase sh
On Fri, Sep 07, 2007 at 04:49:49PM +0530, Arun C Murthy wrote:
>Apache Wiki wrote:
>>== Commit ==
>>
>>When you commit a patch, please:
>>
>> 1. Add an entry in CHANGES.txt, at the end of the appropriate section.
>> This should include the Jira issue id, and the name of the contributor.
>> 1. Inc
[
https://issues.apache.org/jira/browse/HADOOP-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1861:
-
Component/s: dfs
> Update the "how to configure HDFS" documentation to include new featu
Update the "how to configure HDFS" documentation to include new features
Key: HADOOP-1861
URL: https://issues.apache.org/jira/browse/HADOOP-1861
Project: Hadoop
Issue T
I'd like a log4j appender that can write to a Hadoop FileSystem
---
Key: HADOOP-1860
URL: https://issues.apache.org/jira/browse/HADOOP-1860
Project: Hadoop
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/HADOOP-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525812
]
Hadoop QA commented on HADOOP-1833:
---
+1
http://issues.apache.org/jira/secure/attachment/12365302/hbase-stop.patch
[
https://issues.apache.org/jira/browse/HADOOP-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cameron Pope updated HADOOP-120:
Attachment: hadoop-120-workaround.patch
Patch to document ArrayWritable and throw a specific except
[
https://issues.apache.org/jira/browse/HADOOP-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cameron Pope updated HADOOP-120:
Affects Version/s: (was: 0.12.3)
0.15.0
Status: Patch Avai
FSInputDataStream.getPos throws null pointer exception when file has been closed
Key: HADOOP-1859
URL: https://issues.apache.org/jira/browse/HADOOP-1859
Project: Hadoop
[
https://issues.apache.org/jira/browse/HADOOP-1782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated HADOOP-1782:
-
Status: Open (was: Patch Available)
This is now being developed in HADOOP-1298.
> DFS File Per
See http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/226/changes
--
[...truncated 27084 lines...]
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 7.18 sec
[junit] Running org.apache.hadoop.mapred.TestTextOutputFormat
[jun
[
https://issues.apache.org/jira/browse/HADOOP-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525800
]
dhruba borthakur commented on HADOOP-1605:
--
On second thoughts, if the namenode catches exceptions and rest
[
https://issues.apache.org/jira/browse/HADOOP-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1819:
--
Status: Patch Available (was: Open)
> The JobTracker should ensure that it is running on the
[
https://issues.apache.org/jira/browse/HADOOP-1819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Owen O'Malley updated HADOOP-1819:
--
Attachment: jt-init-2.patch
This patch has all of the previous stuff and fixes MiniMR to get r
[
https://issues.apache.org/jira/browse/HADOOP-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525798
]
dhruba borthakur commented on HADOOP-1266:
--
+1. Code looks good.
> Remove DatanodeDescriptor dependency fr
[
https://issues.apache.org/jira/browse/HADOOP-1833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Izaak Rubin updated HADOOP-1833:
Status: Patch Available (was: Open)
Trying on Hudson.
> HBase | bin/stop_hbase.sh returns before
[
https://issues.apache.org/jira/browse/HADOOP-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghu Angadi updated HADOOP-1858:
-
Summary: ".." for ls does not check for existence of its parent directory.
(was: ".." for ls
[
https://issues.apache.org/jira/browse/HADOOP-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghu Angadi updated HADOOP-1858:
-
Description:
'{{bin/hadoop -ls /user/nonexistent/..}}' lists /user even if /user/nonexistent
d
[
https://issues.apache.org/jira/browse/HADOOP-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman updated HADOOP-1847:
--
Status: Patch Available (was: Reopened)
Made constructors and setUp/tearDown public. Works lo
[
https://issues.apache.org/jira/browse/HADOOP-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman updated HADOOP-1847:
--
Attachment: patch.txt
> [hbase] Many HBase tests do not fail well.
> -
[
https://issues.apache.org/jira/browse/HADOOP-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman updated HADOOP-1847:
--
Affects Version/s: (was: 0.16.0)
> [hbase] Many HBase tests do not fail well.
> --
[
https://issues.apache.org/jira/browse/HADOOP-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghu Angadi updated HADOOP-1858:
-
Component/s: dfs
> ".." for ls does check for existence of its parent directory.
>
Hi all,
Is there a way to distinguish between and empty and non-existing directory?
For both cases, we get back the same result.
[EMAIL PROTECTED] ]$ hdfs -ls valid
Found 0 items
[EMAIL PROTECTED] ]$ hdfs -ls invalid
Found 0 items
[EMAIL PROTECTED] ]$
is there a work around for this? I tried -du
".." for ls does check for existence of its parent directory.
--
Key: HADOOP-1858
URL: https://issues.apache.org/jira/browse/HADOOP-1858
Project: Hadoop
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HADOOP-1784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-1784:
--
Attachment: delete1.patch
Patch of work so far. Still have clean up of delete records on compaction to
do.
[
https://issues.apache.org/jira/browse/HADOOP-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525789
]
Jim Kellerman commented on HADOOP-1700:
---
eric baldeschwieler - 06/Sep/07 01:29 AM
> Jim's request that a file
[
https://issues.apache.org/jira/browse/HADOOP-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525786
]
Hadoop QA commented on HADOOP-1351:
---
+1
http://issues.apache.org/jira/secure/attachment/12365360/killTask_v1.9.pa
[
https://issues.apache.org/jira/browse/HADOOP-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman reopened HADOOP-1847:
---
There are still a few tests that have protected constructors and/or setUp and
tearDown methods.
I have been seeing 'Cannot remove data directory' error on different
tests lately. I will take a look.
Raghu.
Christophe Taton (JIRA) wrote:
[ https://issues.apache.org/jira/browse/HADOOP-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525601 ]
Chris
[
https://issues.apache.org/jira/browse/HADOOP-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525767
]
Owen O'Malley commented on HADOOP-785:
--
I withdraw my comment about the secret keys. While it is true, there are
[
https://issues.apache.org/jira/browse/HADOOP-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525766
]
Raghu Angadi commented on HADOOP-1845:
--
> We can try to gather a (new) log but if I remember even the unit test
[
https://issues.apache.org/jira/browse/HADOOP-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525762
]
Hadoop QA commented on HADOOP-1822:
---
+1
http://issues.apache.org/jira/secure/attachment/12365359/1822-2007-09-07a
[
https://issues.apache.org/jira/browse/HADOOP-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HADOOP-1351:
--
Status: Open (was: Patch Available)
> Want to kill a particular task or attempt
> ---
[
https://issues.apache.org/jira/browse/HADOOP-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HADOOP-1351:
--
Status: Patch Available (was: Open)
> Want to kill a particular task or attempt
> ---
[
https://issues.apache.org/jira/browse/HADOOP-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HADOOP-1351:
--
Attachment: killTask_v1.9.patch
After a discussion with Arun in #hadoop, we have decided the f
[
https://issues.apache.org/jira/browse/HADOOP-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christophe Taton updated HADOOP-1822:
-
Attachment: (was: 1822-2007-09-05a.patch)
> Allow SOCKS proxy configuration to remot
[
https://issues.apache.org/jira/browse/HADOOP-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christophe Taton updated HADOOP-1822:
-
Status: Patch Available (was: Open)
JUnit tests run successfully
> Allow SOCKS proxy c
[
https://issues.apache.org/jira/browse/HADOOP-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christophe Taton updated HADOOP-1822:
-
Attachment: 1822-2007-09-07a.patch
Same patch tested successfully again on my machine.
[
https://issues.apache.org/jira/browse/HADOOP-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christophe Taton updated HADOOP-1822:
-
Status: Open (was: Patch Available)
> Allow SOCKS proxy configuration to remotely acces
[
https://issues.apache.org/jira/browse/HADOOP-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525733
]
Enis Soztutar commented on HADOOP-1854:
---
could you please just elaborate more on what features you want?
> H
Hadoop has been used in quite varying cluster sizes (in the range
1-2000), so am strongly in favor of as much automatic configuration as
possible.
Doug Cutting wrote:
Raghu Angadi wrote:
Right now Namenode does not know about the cluster size before
starting IPC server.
Sounds like perhaps
[
https://issues.apache.org/jira/browse/HADOOP-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525723
]
Hadoop QA commented on HADOOP-1818:
---
+1
http://issues.apache.org/jira/secure/attachment/12365351/HADOOP-1818.patc
[
https://issues.apache.org/jira/browse/HADOOP-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Friol updated HADOOP-1818:
-
Affects Version/s: 0.14.1
Status: Patch Available (was: Open)
> MutliFileInputFo
[
https://issues.apache.org/jira/browse/HADOOP-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Friol updated HADOOP-1818:
-
Attachment: HADOOP-1818.patch
Returning empty splits is useless. Here is a patch.
> MutliFileIn
See http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Nightly/225/changes
Changes:
[cutting] HADOOP-1817. Fix MultiFileSplit to read and write the split length,
so that it is not always zero in map tasks. Contributed by Thomas Friol.
[dhruba] HADOOP-1838. The blocksize of files created w
[
https://issues.apache.org/jira/browse/HADOOP-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525694
]
Hadoop QA commented on HADOOP-1351:
---
+1
http://issues.apache.org/jira/secure/attachment/12365334/killTask_v1.8.pa
Apache Wiki wrote:
== Commit ==
When you commit a patch, please:
1. Add an entry in CHANGES.txt, at the end of the appropriate section. This
should include the Jira issue id, and the name of the contributor.
1. Include the Jira issue id in the commit message, along with a short
description
[
https://issues.apache.org/jira/browse/HADOOP-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525676
]
Hadoop QA commented on HADOOP-1856:
---
+1
http://issues.apache.org/jira/secure/attachment/12365332/jarCommand_v02.p
[
https://issues.apache.org/jira/browse/HADOOP-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HADOOP-1351:
--
Status: Patch Available (was: Open)
> Want to kill a particular task or attempt
> ---
[
https://issues.apache.org/jira/browse/HADOOP-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HADOOP-1351:
--
Attachment: killTask_v1.8.patch
latest patch
> Want to kill a particular task or attempt
> -
[
https://issues.apache.org/jira/browse/HADOOP-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HADOOP-1351:
--
Status: Open (was: Patch Available)
Enis, could you please regenerate the patch with trunk? T
[
https://issues.apache.org/jira/browse/HADOOP-1018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HADOOP-1018:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this.
htt
[
https://issues.apache.org/jira/browse/HADOOP-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Yoon updated HADOOP-1856:
Status: Patch Available (was: Open)
re-try
> [Hbase Shell] Jar command using Hadoop RunJar util
[
https://issues.apache.org/jira/browse/HADOOP-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Yoon updated HADOOP-1856:
Status: Open (was: Patch Available)
> [Hbase Shell] Jar command using Hadoop RunJar util
> --
[
https://issues.apache.org/jira/browse/HADOOP-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Yoon updated HADOOP-1856:
Attachment: jarCommand_v02.patch
i used old source.
> [Hbase Shell] Jar command using Hadoop RunJ
Ability to run a script when a task fails to capture stack traces
-
Key: HADOOP-1857
URL: https://issues.apache.org/jira/browse/HADOOP-1857
Project: Hadoop
Issue Type: Improveme
[
https://issues.apache.org/jira/browse/HADOOP-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525652
]
Hadoop QA commented on HADOOP-1351:
---
-1, could not apply patch.
The patch command could not apply the latest atta
[
https://issues.apache.org/jira/browse/HADOOP-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525644
]
Hadoop QA commented on HADOOP-1856:
---
-1, could not apply patch.
The patch command could not apply the latest atta
[
https://issues.apache.org/jira/browse/HADOOP-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enis Soztutar updated HADOOP-1351:
--
Status: Patch Available (was: Open)
> Want to kill a particular task or attempt
> ---
[
https://issues.apache.org/jira/browse/HADOOP-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Yoon updated HADOOP-1856:
Status: Patch Available (was: Open)
> [Hbase Shell] Jar command using Hadoop RunJar util
> --
[
https://issues.apache.org/jira/browse/HADOOP-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Yoon updated HADOOP-1856:
Attachment: jarCommand.patch
{code}
Hbase > jar;
JAR jarFile [mainClass] args...;
Hbase > jar ./b
[
https://issues.apache.org/jira/browse/HADOOP-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525633
]
Torsten Curdt commented on HADOOP-1845:
---
We can try to gather a (new) log but if I remember even the unit test
[Hbase Shell] Jar command using Hadoop RunJar util
--
Key: HADOOP-1856
URL: https://issues.apache.org/jira/browse/HADOOP-1856
Project: Hadoop
Issue Type: Improvement
Components: contr
[
https://issues.apache.org/jira/browse/HADOOP-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Friol updated HADOOP-1818:
-
Summary: MutliFileInputFormat returns "empty" MultiFileSplit when number of
paths < number of sp
[
https://issues.apache.org/jira/browse/HADOOP-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525626
]
Jim Kellerman commented on HADOOP-1793:
---
Committed phase1 - remove TestHClient
> [hbase] Remove deprecated HC
1 - 100 of 102 matches
Mail list logo
