[
https://issues.apache.org/jira/browse/OOZIE-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15032367#comment-15032367
]
Alex Bain commented on OOZIE-2168:
----------------------------------
Thanks to the Oozie community for committing this patch. I wanted to add some
comments to this JIRA for background reference from LinkedIn's perspective.
The name length increase coincides with Azkaban's limitations on workflow name
lengths. Having Oozie and Azkaban name length limits be the same makes it
possible for us to build workflows simultaneously for both Azkaban and Oozie.
These days, we are also using programmatic tools to build our workflows (rather
than editing XML files by hand) - see
https://github.com/linkedin/linkedin-gradle-plugin-for-apache-hadoop/ for more
info. Such tools naturally produce longer workflow names, since these names
usually encode additional metadata-ish information. This is definitely going to
be the way of the world - the 50 char limit was just too short for such tools.
> Oozie flow and action names have 50 char limit
> -----------------------------------------------
>
> Key: OOZIE-2168
> URL: https://issues.apache.org/jira/browse/OOZIE-2168
> Project: Oozie
> Issue Type: Bug
> Components: action
> Reporter: Venkat Ramachandran
> Assignee: Akshay Rai
> Fix For: trunk
>
> Attachments: OOZIE-2168.1.patch, OOZIE-2168.2.patch,
> OOZIE-2168.3.patch, OOZIE-2168.4.patch, OOZIE-2168.5.patch
>
>
> Oozie flow and action names have a 50 character limit and the database fields
> have 256 char limit. So, it will be better to increase this limit to 128+ or
> make it configurable for the deployment.
> The use case is some automated systems create actions and flows names with
> longer character sequence.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
