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 "Hairong Kuang (JIRA)" <ji...@apache.org> on 2011/03/04 22:37:47 UTC
[jira] Created: (HADOOP-7165) listLocatedStatus(path, filter) is
not redefined in FilterFs
listLocatedStatus(path, filter) is not redefined in FilterFs
------------------------------------------------------------
Key: HADOOP-7165
URL: https://issues.apache.org/jira/browse/HADOOP-7165
Project: Hadoop Common
Issue Type: Bug
Components: fs
Reporter: Hairong Kuang
Assignee: Hairong Kuang
Fix For: 0.23.0
listLocatedStatus(path, filter) is not redefined in FilterFs. So if a job client uses a FilterFs to talk to NameNode, it does not trigger the bulk location optimization.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7165) listLocatedStatus(path, filter) is
not redefined in FilterFs
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J updated HADOOP-7165:
----------------------------
Attachment: HADOOP-7165.patch
Rebased patch for trunk.
> listLocatedStatus(path, filter) is not redefined in FilterFs
> ------------------------------------------------------------
>
> Key: HADOOP-7165
> URL: https://issues.apache.org/jira/browse/HADOOP-7165
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 2.0.0-alpha
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Attachments: HADOOP-7165.patch, locatedStatusFilter.patch
>
>
> listLocatedStatus(path, filter) is not redefined in FilterFs. So if a job client uses a FilterFs to talk to NameNode, it does not trigger the bulk location optimization.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7165) listLocatedStatus(path, filter) is
not redefined in FilterFs
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J updated HADOOP-7165:
----------------------------
Target Version/s: 3.0.0
Affects Version/s: 2.0.0-alpha
Status: Patch Available (was: Open)
> listLocatedStatus(path, filter) is not redefined in FilterFs
> ------------------------------------------------------------
>
> Key: HADOOP-7165
> URL: https://issues.apache.org/jira/browse/HADOOP-7165
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 2.0.0-alpha
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Attachments: HADOOP-7165.patch, locatedStatusFilter.patch
>
>
> listLocatedStatus(path, filter) is not redefined in FilterFs. So if a job client uses a FilterFs to talk to NameNode, it does not trigger the bulk location optimization.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (HADOOP-7165) listLocatedStatus(path, filter) is
not redefined in FilterFs
Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002839#comment-13002839 ]
Tsz Wo (Nicholas), SZE commented on HADOOP-7165:
------------------------------------------------
+1 patch looks good.
> listLocatedStatus(path, filter) is not redefined in FilterFs
> ------------------------------------------------------------
>
> Key: HADOOP-7165
> URL: https://issues.apache.org/jira/browse/HADOOP-7165
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.23.0
>
> Attachments: locatedStatusFilter.patch
>
>
> listLocatedStatus(path, filter) is not redefined in FilterFs. So if a job client uses a FilterFs to talk to NameNode, it does not trigger the bulk location optimization.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7165) listLocatedStatus(path, filter) is
not redefined in FilterFs
Posted by "Harsh J (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Harsh J updated HADOOP-7165:
----------------------------
Fix Version/s: (was: 0.24.0)
> listLocatedStatus(path, filter) is not redefined in FilterFs
> ------------------------------------------------------------
>
> Key: HADOOP-7165
> URL: https://issues.apache.org/jira/browse/HADOOP-7165
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Attachments: locatedStatusFilter.patch
>
>
> listLocatedStatus(path, filter) is not redefined in FilterFs. So if a job client uses a FilterFs to talk to NameNode, it does not trigger the bulk location optimization.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (HADOOP-7165) listLocatedStatus(path, filter) is
not redefined in FilterFs
Posted by "Hairong Kuang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hairong Kuang updated HADOOP-7165:
----------------------------------
Attachment: locatedStatusFilter.patch
Here is a straightforward fix.
> listLocatedStatus(path, filter) is not redefined in FilterFs
> ------------------------------------------------------------
>
> Key: HADOOP-7165
> URL: https://issues.apache.org/jira/browse/HADOOP-7165
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.23.0
>
> Attachments: locatedStatusFilter.patch
>
>
> listLocatedStatus(path, filter) is not redefined in FilterFs. So if a job client uses a FilterFs to talk to NameNode, it does not trigger the bulk location optimization.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira