[
https://issues.apache.org/jira/browse/OOZIE-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950269#comment-14950269
]
Akshay Rai commented on OOZIE-2168:
-----------------------------------
Testing JIRA OOZIE-2168
Cleaning local git workspace
----------------------------
+1 PATCH_APPLIES
+1 CLEAN
-1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
-1 the patch contains 2 line(s) longer than 132 characters
+1 the patch does adds/modifies 2 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 197 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 1695
Tests failed: 4
Tests errors: 0
The patch failed the following testcases:
testHostname(org.apache.oozie.servlet.TestHostnameFilter)
testForNoDuplicates(org.apache.oozie.event.TestEventGeneration)
testStreaming(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
testStreamingConfOverride(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)
-1 DISTRO
-1 distro tarball fails with the patch
----------------------------
-1 Overall result, please check the reported -1(s)
There is at least one warning, please check
The full output of the test-patch run is available at
Skipping JIRA update
test-patch exit code: 1
> 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
> 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)
