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

Andras Salamon commented on OOZIE-3573:
---------------------------------------

Thanks for the patch [~arvaiadam] it seems to me you have found other problems 
in the file, like the additional value after the truststore password 
description. I'll rename the Jira according to it.

The test failures also indicate that you've changed some default value which 
caused lots of problems. I think in this change only descriptions should be 
changed and not default values. (If you'd like to change a default value, 
please describe it here and we can discuss it).

I've also realized that you've changed lots of formatting, line breaking, which 
makes it difficult to find the important changes. Can you please upload a patch 
which only contains the real changes.

> Fix oozie-default.xml nameNode.whitelist description
> ----------------------------------------------------
>
>                 Key: OOZIE-3573
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3573
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: Andras Salamon
>            Assignee: Adam Arvai
>            Priority: Minor
>         Attachments: OOZIE-3573-001.patch
>
>
> The nameNode.whitelist section in 
> [oozie-default.xml|https://github.com/apache/oozie/blob/master/core/src/main/resources/oozie-default.xml]
>  contains the following section:
> {noformat}
> <property>
>         <name>oozie.service.HadoopAccessorService.nameNode.whitelist</name>
>         <value> </value>
>         <description>
>             Whitelisted job tracker for Oozie service.
>         </description>
>     </property>
> {noformat}
> This is clearly a block-copy error, description is copied from the previous 
> {{jobTracker.whitelist}} section.
> We should fix it, maybe it would be useful to check the other description 
> fields in the file as well.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to