[
https://issues.apache.org/jira/browse/HADOOP-1969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin Evans resolved HADOOP-1969.
---------------------------------
Resolution: Invalid
I looked into this and the access to the decoder and encoder is synchronized --
multiple threads share the encoder and decoder, but the access is synchronized.
Not a pretty design, as threads will block to use the encoder or decoder, but
also not a bug.
> org.apache.hadoop.io.Text uses static ChasetDecoders, but they aren't
> thread-safe
> ---------------------------------------------------------------------------------
>
> Key: HADOOP-1969
> URL: https://issues.apache.org/jira/browse/HADOOP-1969
> Project: Hadoop
> Issue Type: Bug
> Components: io
> Affects Versions: 0.14.0
> Reporter: Colin Evans
>
> org.apache.hadoop.io.Text uses static instances Text.DECODER and Text.ENCODER
> for all encoding and decoding, but these classes are not thread-safe.
> Multiple threads calling Text.toString() at the same time can cause the
> decoders to output jumbled and garbage data.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
