falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Balu Vellanki (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FALCON-1271) Throw useful exception when workflow/coordinator/bundle file path is > 255 chars
Date Fri, 12 Jun 2015 18:15:00 GMT

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

Balu Vellanki updated FALCON-1271:
----------------------------------
    Description: 
Falcon uses Oozie as its workflow engine and Oozie has a 255 char limit on the length of path
of workflow/coordinator/bundle files. This limit occurs because oozie stores the path in a
OpenJPA database which has  255 char limit for this column. 

Instead of failing with a hard to understand error during run time, it makes sense for Falcon
to check the length of path and throw a more useful exception when an entity is scheduled.


I propose adding a property to runtime.properties. This way, when Oozie changes the limit,
 falcon can update limit without code changes 



  was:
Falcon uses Oozie as its workflow engine and Oozie has a 255 char limit on the length of path
of workflow/coordinator/bundle files. This limit occurs because oozie stores the path in a
OpenJPA database which has  255 char limit for this column. 

Instead of failing with a hard to understand error during run time, it makes sense for Falcon
to check the length of path and throw a more useful exception when an entity is scheduled.





> Throw useful exception when workflow/coordinator/bundle file path is > 255 chars
> --------------------------------------------------------------------------------
>
>                 Key: FALCON-1271
>                 URL: https://issues.apache.org/jira/browse/FALCON-1271
>             Project: Falcon
>          Issue Type: Bug
>          Components: oozie
>    Affects Versions: 0.6.1
>            Reporter: Balu Vellanki
>            Assignee: Balu Vellanki
>             Fix For: 0.7
>
>
> Falcon uses Oozie as its workflow engine and Oozie has a 255 char limit on the length
of path of workflow/coordinator/bundle files. This limit occurs because oozie stores the path
in a OpenJPA database which has  255 char limit for this column. 
> Instead of failing with a hard to understand error during run time, it makes sense for
Falcon to check the length of path and throw a more useful exception when an entity is scheduled.

> I propose adding a property to runtime.properties. This way, when Oozie changes the limit,
 falcon can update limit without code changes 



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

Mime
View raw message