[
https://issues.apache.org/jira/browse/OOZIE-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15855129#comment-15855129
]
Robert Kanter commented on OOZIE-2777:
--------------------------------------
Looks like this is causing a RAT violation. It adds the
{{core/src/test/resources/oldWorkFlowApp.serialized}} binary file, which RAT
flags as not having a correct license. I'll go ahead and make a quick commit
to exclude this file from the check, but we should be more wary of this in
test-patch in the future:
{noformat}
-1 RAT
. -1 the patch seems to introduce 1 new RAT warning(s)
{noformat}
> Config-default.xml longer than 64k results in java.io.UTFDataFormatException
> -----------------------------------------------------------------------------
>
> Key: OOZIE-2777
> URL: https://issues.apache.org/jira/browse/OOZIE-2777
> Project: Oozie
> Issue Type: Bug
> Reporter: Peter Cseh
> Assignee: Peter Cseh
> Fix For: trunk
>
> Attachments: OOZIE-2777-10.patch, OOZIE-2777-11.patch,
> OOZIE-2777-12.patch, OOZIE-2777-13.patch, OOZIE-2777-14.patch,
> OOZIE-2777-1.patch, OOZIE-2777-2.patch, OOZIE-2777-3.patch,
> OOZIE-2777-4.patch, OOZIE-2777-5.patch, OOZIE-2777-7.patch,
> OOZIE-2777-8.patch, OOZIE-2777-9.patch
>
>
> OOZIE-1642 introduced a workaround for DataOutputStream's 64k limit for
> Strings.
> We've encountered the same error when a config-default.xml is larger than the
> limit.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
