[
https://issues.apache.org/jira/browse/OOZIE-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840174#comment-15840174
]
Rohini Palaniswamy commented on OOZIE-2777:
-------------------------------------------
bq. Won't this patch break for workflows that were in running state during
upgrade?
Ignore that comment. It is handled.
Looks like you have used the new method for all strings. I think it is
unnecessary overhead for things like entry.getKey() which would not even come
to 1K.
> 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)
