Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <797171025.159181263237474406.JavaMail.jira@brutus.apache.org>
Date: Mon, 11 Jan 2010 19:17:54 +0000 (UTC)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-1358) Utils.OutputLogFilter
 incorrectly filters for _logs
In-Reply-To: <1272292882.58621262742594437.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-1358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798794#action_12798794 ] 

Todd Lipcon commented on MAPREDUCE-1358:
----------------------------------------

Amar: I don't think so - that wouldn't filter a file like /foo/_logs/bar - right? I don't think there's any contract that PathFilter is called in a pre-order traversal, so filtering /foo/_logs doesn't guarantee that /foo/_logs/bar will get automatically filtered.

> Utils.OutputLogFilter incorrectly filters for _logs
> ---------------------------------------------------
>
>                 Key: MAPREDUCE-1358
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1358
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>         Attachments: mapreduce-1358.txt
>
>
> OutputLogFilter checks if the path contains _logs. This would incorrectly filter out all contents of a directory called server_logs, for example. Instead it should check for a path component exactly equal to _logs

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.