[
https://issues.apache.org/jira/browse/OOZIE-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Burak Gursoy updated OOZIE-2025:
--------------------------------
Description:
Hi,
There is a limitation on action name lengths and the limit for that is too low:
private static final int MAX_NODE_NAME_LEN = 50; // [1]
You can easily hit that limit if the action names are auto generated and a bit
verbose to have them meaningful names (for visual checking/debugging the
resulting workflow.xml).
There are two workarounds:
i) hash the generated names (will make them obscure for human eyes)
ii) substring the actual name until 35-40 chars and append a random string for
the remaining 10 chars (that's what we're doing-- but still not very convenient)
The limit can still be there but it will be really nice to have either:
- Increase to something like 200 -- or even higher
- The limit can be converted into an overridable configuration section, which
will solve the problem completely for the users.
Also I think such limits need to be checked with the `oozie validate` command
as well as such xmls shouldn't pass as valid if there is a limitation.
Thanks,
Burak
[1]
https://git-wip-us.apache.org/repos/asf?p=oozie.git;a=blob;f=core/src/main/java/org/apache/oozie/util/ParamChecker.java;h=825c0b061e647424acfa2daa579a044592ea1869;hb=master#l109
was:
Hi,
There is a limitation on action name lengths and the limit for that is too low:
private static final int MAX_NODE_NAME_LEN = 50; // [1]
You can easily hit that limit if the action names are auto generated and a bit
verbose to have them meaningful names (for visual checking/debugging the
resulting workflow.xml).
There are two workarounds:
i) hash the generated names (will make them obscure for human eyes)
ii) substring the actual name until 35-40 chars and append a random string for
the remaining 10 chars (that's what we're doing-- but still not very convenient)
The limit can still be there but it will be really nice to have either:
- Increase to something like 200 -- or even higher
- The limit can be converted into an overridable configuration section, which
will solve the problem completely for the users.
Thanks,
Burak
[1]
https://git-wip-us.apache.org/repos/asf?p=oozie.git;a=blob;f=core/src/main/java/org/apache/oozie/util/ParamChecker.java;h=825c0b061e647424acfa2daa579a044592ea1869;hb=master#l109
> MAX_NODE_NAME_LEN is too small for auto generated action names
> --------------------------------------------------------------
>
> Key: OOZIE-2025
> URL: https://issues.apache.org/jira/browse/OOZIE-2025
> Project: Oozie
> Issue Type: Bug
> Reporter: Burak Gursoy
> Priority: Minor
>
> Hi,
> There is a limitation on action name lengths and the limit for that is too
> low:
> private static final int MAX_NODE_NAME_LEN = 50; // [1]
> You can easily hit that limit if the action names are auto generated and a
> bit verbose to have them meaningful names (for visual checking/debugging the
> resulting workflow.xml).
> There are two workarounds:
> i) hash the generated names (will make them obscure for human eyes)
> ii) substring the actual name until 35-40 chars and append a random string
> for the remaining 10 chars (that's what we're doing-- but still not very
> convenient)
> The limit can still be there but it will be really nice to have either:
> - Increase to something like 200 -- or even higher
> - The limit can be converted into an overridable configuration section, which
> will solve the problem completely for the users.
> Also I think such limits need to be checked with the `oozie validate` command
> as well as such xmls shouldn't pass as valid if there is a limitation.
> Thanks,
> Burak
> [1]
> https://git-wip-us.apache.org/repos/asf?p=oozie.git;a=blob;f=core/src/main/java/org/apache/oozie/util/ParamChecker.java;h=825c0b061e647424acfa2daa579a044592ea1869;hb=master#l109
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
