Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hadoop-dev@lucene.apache.org
Message-ID: <27990952.1187387670968.JavaMail.jira@brutus>
Date: Fri, 17 Aug 2007 14:54:30 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: hadoop-dev@lucene.apache.org
Subject: [jira] Commented: (HADOOP-1436) Redesign Tool and ToolBase API and
 releted functionality
In-Reply-To: <10697301.1180122676437.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-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520685 ] 

Doug Cutting commented on HADOOP-1436:
--------------------------------------

This looks reasonable to me.  Does anyone have any objections, or should I commit this?

> Redesign Tool and ToolBase API and releted functionality
> --------------------------------------------------------
>
>                 Key: HADOOP-1436
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1436
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: util
>    Affects Versions: 0.15.0
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 0.15.0
>
>         Attachments: redesignToolAndRelated_v1.0.patch, redesignToolAPI_v1.1.patch, redesignToolAPI_v1.2.patch, redesignToolAPI_v1.3.patch
>
>
> With the discussion from HADOOP-1425, we need better abstraction and better tool runner utilities. 
> 1. Classes do not need to extend ToolBase 
> 2. functions for parsing general HadoopCommands (-fs, -conf, -jt) should be public
> 3. We need a ToolRunner, or similar functionality 
> 4. Also we need each class (implementing Tool) to be runnable (main method)
> 5. CLI objects can be passed to run method of the Tool class (arguable)

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