[
https://issues.apache.org/jira/browse/HADOOP-7940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13263528#comment-13263528
]
Harsh J commented on HADOOP-7940:
---------------------------------
Jim - I'm actually not convinced this hurts at all. I've decided not to have
this reverted in second thought, and I've explained the reasoning at
HADOOP-8323.
Clear call ought to clear memory and thats what this change actually intends to
do (though the test case may lead you astray - filed HADOOP-8324).
The current javadocs indeed cover the getBytes usage behavior as you've pointed
out. So if you'd like to keep the size in its increased state, why clear() it?
> method clear() in org.apache.hadoop.io.Text does not work
> ---------------------------------------------------------
>
> Key: HADOOP-7940
> URL: https://issues.apache.org/jira/browse/HADOOP-7940
> Project: Hadoop Common
> Issue Type: Bug
> Components: io
> Affects Versions: 0.20.205.0
> Environment: Ubuntu, hadoop cloudera CDH3U2, Oracle SUN JDK 6U30
> Reporter: Aaron,
> Assignee: Csaba Miklos
> Labels: patch
> Fix For: 2.0.0
>
> Attachments: HADOOP-7940.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> LineReader reader = new LineReader(in, 4096);
> ...
> Text text = new Text();
> while((reader.readLine(text)) > 0) {
> ...
> text.clear();
> }
> }
> Even the clear() method is called each time, some bytes are still not filled
> as zero.
> So, when reader.readLine(text) is called in a loop, some bytes are dirty
> which was from last call.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
