[
https://issues.apache.org/jira/browse/OOZIE-2777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15839890#comment-15839890
]
Peter Cseh commented on OOZIE-2777:
-----------------------------------
Thanks for the review [~qwertymaniac]!
I've removed the imports and added comments about the old format. The null
value check may come in handy for different implementations of DataOutput.
I don't think checking the size of the byte array is necessary. I don't know
what would be a good upper limit and for negative values, we'll fail anyways.
> 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)
