[jira] [Commented] (FALCON-1271) Throw useful exception when workflow/coordinator/bundle file path is > 255 chars

["Shaik Idris Ali (JIRA)" <ji...@apache.org>]

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

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

This is very specific to oozie, and in our production system we have changed the limit in oozie, if I remember correctly in oozie DB the column type is changed from CHAR to VARCHAR. And I think in most production system we will hit the limit of 255 chars.

Its a good idea to throw the useful exception, however I fee Falcon should not explicitly check for this limit. 

Also, the oozie DB default column size limit hits at other instances as well, ex: A resolved workflow instances with too many input paths fails with JPA exception. I would suggest not to add any additional checks which are specific to oozie.

> 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
>
>         Attachments: FALCON-1271.patch
>
>
> 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)