[
https://issues.apache.org/jira/browse/FALCON-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14604578#comment-14604578
]
Srikanth Sundarrajan commented on FALCON-1271:
----------------------------------------------
[~bvellanki], Even if we were to apply the check, failing the schedule while
allowing the submit in falcon might confuse the user.
> 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)
