You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Boris Shkolnik (JIRA)" <ji...@apache.org> on 2010/03/10 23:17:27 UTC
[jira] Created: (HADOOP-6627) "Bad Connection to FS" message in
FSShell should print message from the exception
"Bad Connection to FS" message in FSShell should print message from the exception
---------------------------------------------------------------------------------
Key: HADOOP-6627
URL: https://issues.apache.org/jira/browse/HADOOP-6627
Project: Hadoop Common
Issue Type: Bug
Reporter: Boris Shkolnik
We don't need the trace, but at lease some hint of what happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6627) "Bad Connection to FS" message in
FSShell should print message from the exception
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-6627:
-----------------------------------
Status: Patch Available (was: Open)
> "Bad Connection to FS" message in FSShell should print message from the exception
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-6627
> URL: https://issues.apache.org/jira/browse/HADOOP-6627
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6627-BP20.patch, HADOOP-6627.patch
>
>
> We don't need the trace, but at lease some hint of what happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6627) "Bad Connection to FS" message in
FSShell should print message from the exception
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-6627:
-----------------------------------
Status: Resolved (was: Patch Available)
Resolution: Fixed
no test , because text change only.
Committed to trunk.
> "Bad Connection to FS" message in FSShell should print message from the exception
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-6627
> URL: https://issues.apache.org/jira/browse/HADOOP-6627
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6627-BP20.patch, HADOOP-6627.patch, HADOOP-6627.patch
>
>
> We don't need the trace, but at lease some hint of what happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HADOOP-6627) "Bad Connection to FS" message in
FSShell should print message from the exception
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik reassigned HADOOP-6627:
--------------------------------------
Assignee: Boris Shkolnik
> "Bad Connection to FS" message in FSShell should print message from the exception
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-6627
> URL: https://issues.apache.org/jira/browse/HADOOP-6627
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
>
> We don't need the trace, but at lease some hint of what happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6627) "Bad Connection to FS" message in
FSShell should print message from the exception
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-6627:
-----------------------------------
Attachment: HADOOP-6627.patch
> "Bad Connection to FS" message in FSShell should print message from the exception
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-6627
> URL: https://issues.apache.org/jira/browse/HADOOP-6627
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6627-BP20.patch, HADOOP-6627.patch
>
>
> We don't need the trace, but at lease some hint of what happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6627) "Bad Connection to FS" message in
FSShell should print message from the exception
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871319#action_12871319 ]
Hudson commented on HADOOP-6627:
--------------------------------
Integrated in Hadoop-Common-trunk #346 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk/346/])
> "Bad Connection to FS" message in FSShell should print message from the exception
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-6627
> URL: https://issues.apache.org/jira/browse/HADOOP-6627
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6627-BP20.patch, HADOOP-6627.patch, HADOOP-6627.patch
>
>
> We don't need the trace, but at lease some hint of what happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6627) "Bad Connection to FS" message in
FSShell should print message from the exception
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868433#action_12868433 ]
Hadoop QA commented on HADOOP-6627:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12444741/HADOOP-6627.patch
against trunk revision 944521.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/524/console
This message is automatically generated.
> "Bad Connection to FS" message in FSShell should print message from the exception
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-6627
> URL: https://issues.apache.org/jira/browse/HADOOP-6627
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6627-BP20.patch, HADOOP-6627.patch
>
>
> We don't need the trace, but at lease some hint of what happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6627) "Bad Connection to FS" message in
FSShell should print message from the exception
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-6627:
-----------------------------------
Status: Patch Available (was: Open)
> "Bad Connection to FS" message in FSShell should print message from the exception
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-6627
> URL: https://issues.apache.org/jira/browse/HADOOP-6627
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6627-BP20.patch, HADOOP-6627.patch, HADOOP-6627.patch
>
>
> We don't need the trace, but at lease some hint of what happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6627) "Bad Connection to FS" message in
FSShell should print message from the exception
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-6627:
-----------------------------------
Attachment: HADOOP-6627.patch
> "Bad Connection to FS" message in FSShell should print message from the exception
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-6627
> URL: https://issues.apache.org/jira/browse/HADOOP-6627
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6627-BP20.patch, HADOOP-6627.patch, HADOOP-6627.patch
>
>
> We don't need the trace, but at lease some hint of what happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6627) "Bad Connection to FS" message in
FSShell should print message from the exception
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868459#action_12868459 ]
Hadoop QA commented on HADOOP-6627:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12444745/HADOOP-6627.patch
against trunk revision 944521.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/527/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/527/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/527/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h4.grid.sp2.yahoo.net/527/console
This message is automatically generated.
> "Bad Connection to FS" message in FSShell should print message from the exception
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-6627
> URL: https://issues.apache.org/jira/browse/HADOOP-6627
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6627-BP20.patch, HADOOP-6627.patch, HADOOP-6627.patch
>
>
> We don't need the trace, but at lease some hint of what happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (HADOOP-6627) "Bad Connection to FS" message in
FSShell should print message from the exception
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868883#action_12868883 ]
Hudson commented on HADOOP-6627:
--------------------------------
Integrated in Hadoop-Common-trunk-Commit #256 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk-Commit/256/])
HADOOP-6627. 'Bad Connection to FS' message in FSShell should print message from the exception
> "Bad Connection to FS" message in FSShell should print message from the exception
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-6627
> URL: https://issues.apache.org/jira/browse/HADOOP-6627
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6627-BP20.patch, HADOOP-6627.patch, HADOOP-6627.patch
>
>
> We don't need the trace, but at lease some hint of what happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6627) "Bad Connection to FS" message in
FSShell should print message from the exception
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-6627:
-----------------------------------
Attachment: HADOOP-6627-BP20.patch
for previous version. Not for commit.
> "Bad Connection to FS" message in FSShell should print message from the exception
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-6627
> URL: https://issues.apache.org/jira/browse/HADOOP-6627
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6627-BP20.patch
>
>
> We don't need the trace, but at lease some hint of what happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HADOOP-6627) "Bad Connection to FS" message in
FSShell should print message from the exception
Posted by "Boris Shkolnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-6627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Boris Shkolnik updated HADOOP-6627:
-----------------------------------
Status: Open (was: Patch Available)
> "Bad Connection to FS" message in FSShell should print message from the exception
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-6627
> URL: https://issues.apache.org/jira/browse/HADOOP-6627
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Boris Shkolnik
> Assignee: Boris Shkolnik
> Attachments: HADOOP-6627-BP20.patch, HADOOP-6627.patch, HADOOP-6627.patch
>
>
> We don't need the trace, but at lease some hint of what happened.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.