[
https://issues.apache.org/jira/browse/HADOOP-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521686
]
Enis Soztutar commented on HADOOP-1436:
---------------------------------------
If i were a regular hadoop user, i would prefer the issue that deprecates
anything to be listed in Incompatible changes. A hadoop client, could easily
ignore improvements, optimizations and bug fixes sections and go for only new
features and incompatible changes.
I agree with the deprecation/removal cycle, but i do no see any
counter-argument against listing both changes in incompatible changes. Notice
also that HADOOP-1621 is already listed in incompatible changes section.
> 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.
