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

Kengo Seki updated HADOOP-11903:
--------------------------------
    Description: 
As for java, it 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. 

  was:
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. 


> 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
>
>
> As for java, it 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)

Reply via email to