falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shaik Idris Ali (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-255) Rename falcon workflow variable names
Date Wed, 09 Apr 2014 11:18:15 GMT

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

Shaik Idris Ali commented on FALCON-255:
----------------------------------------

Hi [~gibbus], we need to ensure backward compatibility as [~sriksun] mentioned.

{code}
-        String logDir = properties.getProperty("logDir");
+        String logDir = properties.getProperty("falconLogDir");
{code}
the processes scheduled prior to Falcon upgrade will still be setting logDir and not falconLogDir.

So, we need to take care of these classes as the execution logic is global to all processes.
LateRerunConsumer
LateRerunHandler



> Rename falcon workflow variable names
> -------------------------------------
>
>                 Key: FALCON-255
>                 URL: https://issues.apache.org/jira/browse/FALCON-255
>             Project: Falcon
>          Issue Type: Bug
>            Reporter: Shwetha G S
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 0.5
>
>         Attachments: FALCON-255.patch
>
>
> The workflow variable names used by falcon should have falcon-specific format so that
they don't collide with user-defined variable names.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message