Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <198549057.1226968964415.JavaMail.jira@brutus>
Date: Mon, 17 Nov 2008 16:42:44 -0800 (PST)
From: "Owen O'Malley (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-4668) Improve JavaDoc on
 JobConf.setCombinerClass to better document restrictions on combiners
In-Reply-To: <1392962846.1226877524246.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-4668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Owen O'Malley updated HADOOP-4668:
----------------------------------

    Status: Patch Available  (was: Open)

> Improve JavaDoc on JobConf.setCombinerClass to better document restrictions on combiners
> ----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-4668
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4668
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>         Attachments: combiner-doc.patch
>
>
> It is often not clear to developers that Combiners may be called 0, 1, or many times and that combiners input and output types must be the same and the combiner must not have side effects. Since there isn't a Combiner class, the best place to put this documentation is on JobConf.setCombinerClass.

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