[
https://issues.apache.org/jira/browse/OOZIE-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840191#comment-15840191
]
Peter Cseh commented on OOZIE-2777:
-----------------------------------
Thanks for the comment [~rohini]!
Yes, Oozie should be able to handle serialized things from before the patch.
After I've found that there are already two workarounds for the same issue,
I've figured the overhead would be small enough for short strings for the
benefit to avoid this issue in the future.
I can remove the usage of StringSerializationUtil for cases when we know that
what we're writing will be small.
> 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
> Attachments: OOZIE-2777-10.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.4#6332)
