You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Shaik Idris Ali (JIRA)" <ji...@apache.org> on 2014/04/09 13:18:15 UTC

[jira] [Commented] (FALCON-255) Rename falcon workflow variable names

    [ 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)