tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "TezQA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEZ-2613) Fetcher(unordered) using List to store InputAttemptIdentifier can lead to some inefficiency during remove() operation
Date Mon, 27 Jul 2015 16:16:05 GMT

    [ https://issues.apache.org/jira/browse/TEZ-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14642936#comment-14642936
] 

TezQA commented on TEZ-2613:
----------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  http://issues.apache.org/jira/secure/attachment/12747356/TEZ-2613.4.patch
  against master revision b9d5c20.

    {color:red}-1 patch{color}.  master compilation may be broken.

Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/923//console

This message is automatically generated.

> Fetcher(unordered) using List to store InputAttemptIdentifier can lead to some inefficiency
during remove() operation
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: TEZ-2613
>                 URL: https://issues.apache.org/jira/browse/TEZ-2613
>             Project: Apache Tez
>          Issue Type: Improvement
>            Reporter: Saikat
>            Assignee: Saikat
>         Attachments: TEZ-2613.1.patch, TEZ-2613.2.patch, TEZ-2613.3.patch, TEZ-2613.4.patch,
TEZ-2613.patch
>
>
> remove() operation on the remaining list can be inefficient. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message