You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Kengo Seki (JIRA)" <ji...@apache.org> on 2015/07/08 04:00:07 UTC

[jira] [Commented] (HADOOP-11903) test-patch plugin for checking file name conventions

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

Kengo Seki commented on HADOOP-11903:
-------------------------------------

Updated the summary and description. Please correct if there is something wrong.

> test-patch plugin for checking file name conventions
> ----------------------------------------------------
>
>                 Key: HADOOP-11903
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11903
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: yetus
>    Affects Versions: HADOOP-12111
>            Reporter: Allen Wittenauer
>            Assignee: Kengo Seki
>         Attachments: HADOOP-11903.HADOOP-12111.00.patch
>
>
> Providing yetus with the functionality to detect newly added files which doesn't follow the naming conventions. As for java, it also can be used for checking classnames. In the past, we've named things like DefaultResourceCalculator, DefaultContainerExecutor, and DefaultCodec that do nothing but cause problems down the road since they are effectively version and functionality locked forever.  If these examples had been named what they truly were (e.g., MemoryResourceCalculator, SimpleContainerExecutor, and GZipCodec), the defaults could then be changed in the future in a compatible way. One way to enforce this is to prevent the creation of new classes called Default-anything. 



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