[
https://issues.apache.org/jira/browse/HADOOP-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517672
]
Joydeep Sen Sarma commented on HADOOP-939:
--
am a new hadoop user - i am looking into how much of a warehouse
[
https://issues.apache.org/jira/browse/HADOOP-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517669
]
Konstantin Shvachko commented on HADOOP-1506:
-
What is the reason for keeping the same block size in the
[
https://issues.apache.org/jira/browse/HADOOP-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517665
]
Jim Kellerman commented on HADOOP-1678:
---
The region server that performed the split should serve the lower hal
[
https://issues.apache.org/jira/browse/HADOOP-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman resolved HADOOP-1466.
---
Resolution: Fixed
Cleaned up all but HBase Shell. Resolving issue.
> Clean up warnings, vis
[
https://issues.apache.org/jira/browse/HADOOP-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517646
]
Hairong Kuang commented on HADOOP-1665:
---
There is a subtle implication introduced by the above approach. Assum
[
https://issues.apache.org/jira/browse/HADOOP-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lohit updated HADOOP-1663:
--
Attachment: h-1663-streamexception-simpletestcase.patch
Sorry had updated with wrong patch. Correct patch upda
[
https://issues.apache.org/jira/browse/HADOOP-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lohit updated HADOOP-1663:
--
Attachment: (was: h-1663-streamexception-simpletestcase.patch)
> streaming returning 0 when submitJob fail
[
https://issues.apache.org/jira/browse/HADOOP-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1665:
-
Attachment: Trash2.patch
A unit test to test deleting directories.
> DFS Trash feature
[
https://issues.apache.org/jira/browse/HADOOP-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1665:
-
Attachment: (was: Trash.patch)
> DFS Trash feature bugs
> --
>
>
[
https://issues.apache.org/jira/browse/HADOOP-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HADOOP-1662:
--
Attachment: fastsplits.patch
First cut at fast splits. Missing a cleanup thread and still undergoing
testing
[
https://issues.apache.org/jira/browse/HADOOP-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517636
]
lohit commented on HADOOP-1663:
---
Tested Koji's patch and included a test case for the same. Right now have a
simple t
[
https://issues.apache.org/jira/browse/HADOOP-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lohit updated HADOOP-1663:
--
Attachment: h-1663-streamexception-simpletestcase.patch
Updated patch with simple test case
> streaming retur
Re organize StreamJob::submitAndMonitorJob() Exception handling
---
Key: HADOOP-1681
URL: https://issues.apache.org/jira/browse/HADOOP-1681
Project: Hadoop
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HADOOP-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517630
]
Hadoop QA commented on HADOOP-1595:
---
-1, build or testing failed
2 attempts failed to build and test the latest a
[
https://issues.apache.org/jira/browse/HADOOP-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-1565:
-
Resolution: Fixed
Fix Version/s: 0.15.0
Status: Resolved (was: Patch A
[
https://issues.apache.org/jira/browse/HADOOP-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517624
]
dhruba borthakur commented on HADOOP-785:
-
+1. I like this current proposal of splitting up the config into t
[
https://issues.apache.org/jira/browse/HADOOP-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517617
]
Raghu Angadi commented on HADOOP-1680:
--
NAMENODE:
* Safe mode will be turned off automatically upon completio
Improvements to Block CRC upgrade messages
--
Key: HADOOP-1680
URL: https://issues.apache.org/jira/browse/HADOOP-1680
Project: Hadoop
Issue Type: Bug
Affects Versions: 0.14.0
Reporter:
[
https://issues.apache.org/jira/browse/HADOOP-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy resolved HADOOP-1676.
---
Resolution: Duplicate
Ok, after a discussion with Devaraj, this is a duplicate of HADOOP-150
[
https://issues.apache.org/jira/browse/HADOOP-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devaraj Das reopened HADOOP-1676:
-
Assignee: Arun C Murthy
Speaking on behalf of Runping ^smile^. This exception is seen with 0.1
[
https://issues.apache.org/jira/browse/HADOOP-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy resolved HADOOP-1676.
---
Resolution: Invalid
This looks like a misunderstanding, the stack trace came from HADOOP-119
[
https://issues.apache.org/jira/browse/HADOOP-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE updated HADOOP-1595:
---
Status: Patch Available (was: Open)
> Add an option to setReplication metho
[
https://issues.apache.org/jira/browse/HADOOP-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE updated HADOOP-1595:
---
Attachment: 1595_20070803.patch
I was wrong: it failed on my tests last few
[
https://issues.apache.org/jira/browse/HADOOP-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE updated HADOOP-1595:
---
Attachment: (was: 1595_20070802.patch)
> Add an option to setReplication
[
https://issues.apache.org/jira/browse/HADOOP-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tsz Wo (Nicholas), SZE updated HADOOP-1595:
---
Status: Open (was: Patch Available)
> Add an option to setReplication metho
[
https://issues.apache.org/jira/browse/HADOOP-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517601
]
Devaraj Das commented on HADOOP-1675:
-
This can happen if the InMemoryFileSystem instance is "closed". The
InMe
[hbase] Add version into hbase build
Key: HADOOP-1679
URL: https://issues.apache.org/jira/browse/HADOOP-1679
Project: Hadoop
Issue Type: Improvement
Components: contrib/hbase
Reporte
[hbase] On region split, master should designate which host should serve
daughter splits
Key: HADOOP-1678
URL: https://issues.apache.org/jira/browse/HADOOP-1678
[
https://issues.apache.org/jira/browse/HADOOP-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nigel Daley reassigned HADOOP-1665:
---
Assignee: dhruba borthakur (was: Doug Cutting)
> DFS Trash feature bugs
> -
Any other know incompatibilities (API, protocol, layout) between 0.13
and 0.14?
Owen? Dhruba? Others?
On Jul 31, 2007, at 5:13 PM, Raghu Angadi (JIRA) wrote:
[ https://issues.apache.org/jira/browse/HADOOP-1668?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel#ac
improve semantics of the hadoop dfs command
---
Key: HADOOP-1677
URL: https://issues.apache.org/jira/browse/HADOOP-1677
Project: Hadoop
Issue Type: Improvement
Components: dfs
Rep
java.lang.Exception at
org.apache.hadoop.io.compress.zlib.ZlibFactory.getZlibDecompressor(ZlibFactory.java:107)
---
Key: HADOOP-1676
URL: https://issues.ap
[
https://issues.apache.org/jira/browse/HADOOP-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517588
]
Jim Kellerman commented on HADOOP-1644:
---
Compactions should never block updates.
What follows is a proposed s
[
https://issues.apache.org/jira/browse/HADOOP-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman updated HADOOP-1466:
--
Summary: Clean up warnings, visibility and javadoc issues in HBase (was:
Clean up visibility
[
https://issues.apache.org/jira/browse/HADOOP-1675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Runping Qi updated HADOOP-1675:
---
Description:
In a job running release .13, I saw a lot of failures due to the following
errors:
2
Null pointer exception in InMemoryFileSystem
Key: HADOOP-1675
URL: https://issues.apache.org/jira/browse/HADOOP-1675
Project: Hadoop
Issue Type: Bug
Components: mapred
Affects Versio
[
https://issues.apache.org/jira/browse/HADOOP-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Kellerman updated HADOOP-1644:
--
Fix Version/s: 0.15.0
Priority: Major (was: Minor)
Issue Type: Imp
[
https://issues.apache.org/jira/browse/HADOOP-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517561
]
Arun C Murthy edited comment on HADOOP-785 at 8/3/07 8:31 AM:
--
bq. To summarize, we migh
[
https://issues.apache.org/jira/browse/HADOOP-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517561
]
Arun C Murthy commented on HADOOP-785:
--
bq. To summarize, we might end up having a couple of duplicate config it
[
https://issues.apache.org/jira/browse/HADOOP-785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517538
]
Devaraj Das commented on HADOOP-785:
bq. I'd rather keep hadoop-default.xml sacrosanct, though we don't prevent y
[
https://issues.apache.org/jira/browse/HADOOP-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edward yoon updated HADOOP-1672:
Attachment: hbaseshell_v03.patch
> HBase Shell should use new client classes
> ---
[
https://issues.apache.org/jira/browse/HADOOP-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
edward yoon updated HADOOP-1672:
Attachment: hbaseshell_v02.patch
Re-upload, Trivial changes.
> HBase Shell should use new client
42 matches
Mail list logo