[
https://issues.apache.org/jira/browse/HADOOP-6004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718977#action_12718977
]
Jakob Homan commented on HADOOP-6004:
-------------------------------------
bq. What kind of issues would this problem cause?
Since the arrays were not resized before trying to assign new values, if you
were trying to deserialize a BL with multiple hosts or topologyPaths, you would
get an array index out of bounds exception, which is a runtime exception and
wouldn't have been caught. Since this happened, there must be no code that's
trying to do. The deserialization is still broken and should be fixed though.
bq. Is only trunk affected?
I checked back to the 18.3 code and this problem is there. It would probably be
a good idea to do a patch for that version as well.
> BlockLocation deserialization is incorrect
> ------------------------------------------
>
> Key: HADOOP-6004
> URL: https://issues.apache.org/jira/browse/HADOOP-6004
> Project: Hadoop Core
> Issue Type: Bug
> Components: fs
> Reporter: Jakob Homan
> Assignee: Jakob Homan
> Attachments: HADOOP-6004.patch
>
>
> The {{readFields}} method of {{BlockLocation}} does not correctly allocate
> new arrays for topologyPaths and hosts. Patch shortly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
