ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Don Bosco Durai <bo...@apache.org>
Subject Re: [jira] [Commented] (RANGER-969) Property ranger.usersync.filesource.text.delimiter mis-spelled
Date Thu, 05 May 2016 05:21:26 GMT
+1 

This will provide backward compatibility.

Bosco





On 5/4/16, 10:20 PM, "Madhan Neethiraj (JIRA)" <jira@apache.org> wrote:

>
>    [ https://issues.apache.org/jira/browse/RANGER-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271894#comment-15271894
] 
>
>Madhan Neethiraj commented on RANGER-969:
>-----------------------------------------
>
>As [~bbende] mentioned in his email to dev list, some deployments might already be using
this mis-spelled property. To ensure that such deployments don't break after fixing the spelling
error, please consider the following:
>
>{code}
>    public String getUserSyncFileSourceDelimiter() {
>        String val = prop.getProperty("ranger.usersync.filesource.text.delimiter");
>
>        if(val == null) {
>            val = prop.getProperty("ranger.usersync.filesource.text.delimiterer"); //
look with mis-spelled property-name used earlier
>
>            if(val == null) {
>                val = DEFAULT_USER_GROUP_TEXTFILE_DELIMITER;
>            }
>        }
>
>        return val;
>    }
>{code}
>
>> Property ranger.usersync.filesource.text.delimiter mis-spelled
>> --------------------------------------------------------------
>>
>>                 Key: RANGER-969
>>                 URL: https://issues.apache.org/jira/browse/RANGER-969
>>             Project: Ranger
>>          Issue Type: Bug
>>            Reporter: Bryan Bende
>>            Assignee: Bryan Bende
>>            Priority: Minor
>>             Fix For: 0.6.0
>>
>>
>> The property is spelled as ranger.usersync.filesource.text.delimiterer in UserGroupSyncConfig.java.
>
>
>
>--
>This message was sent by Atlassian JIRA
>(v6.3.4#6332)


Mime
View raw message