You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Srikanth Sundarrajan (JIRA)" <ji...@apache.org> on 2014/11/10 04:50:33 UTC

[jira] [Commented] (FALCON-320) Whitespace has not been taken into consideration in runtime.properties

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

Srikanth Sundarrajan commented on FALCON-320:
---------------------------------------------

Does it also make sense to override and implement ApplicationProperties::getProperty() to protect against trailing space. Patch certainly fixes issue being reported, but was wondering if that additionally also needs to be addressed.

> Whitespace has not been taken into consideration in runtime.properties
> ----------------------------------------------------------------------
>
>                 Key: FALCON-320
>                 URL: https://issues.apache.org/jira/browse/FALCON-320
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Karishma Gulati
>            Assignee: Ajay Yadav
>            Priority: Minor
>         Attachments: FALCON-320.patch
>
>
> In falcon runtime.properties, while configuring all servers with the prism, 
> #### To configure falcon servers with prism ####
> *.all.colos=abc, xyz
> if a space is added after the comma, the space is included in the second colo's name. 
> So, a cluster on colo "xyz" does not submit. 
> We get the following error:
> xyz/org.apache.falcon.FalconException::java.lang.IllegalArgumentException



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