Mailing-List: contact dev-help@falcon.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.incubator.apache.org
Date: Mon, 17 Nov 2014 10:01:33 +0000 (UTC)
From: "Ajay Yadav (JIRA)" <jira@apache.org>
To: dev@falcon.incubator.apache.org
Message-ID: <JIRA.12696882.1393236715000.513955.1416218493969@Atlassian.JIRA>
In-Reply-To: <JIRA.12696882.1393236715000@Atlassian.JIRA>
References: <JIRA.12696882.1393236715000@Atlassian.JIRA>
 <JIRA.12696882.1393236715384@arcas>
Subject: [jira] [Updated] (FALCON-320) Whitespace has not been taken into
 consideration in runtime.properties
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ajay Yadav updated FALCON-320:
------------------------------
    Attachment: FALCON-320-v2.patch

Added unit tests. 

> 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
>    Affects Versions: 0.6
>            Reporter: Karishma Gulati
>            Assignee: Ajay Yadav
>            Priority: Minor
>         Attachments: FALCON-320-v1.patch, FALCON-320-v2.patch, 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)