[
https://issues.apache.org/jira/browse/HBASE-7215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13505264#comment-13505264
]
stack commented on HBASE-7215:
------------------------------
I changed my mind about MutateResult. We are already going to be pissing
people off. We can let Result as is w/ its copyFrom for mapred.
Will do as you suggest.
Will have a go at the MR stuff tomorrow too... (looks ugly).
> Put, Delete, Increment, and Result still implement Writable
> -----------------------------------------------------------
>
> Key: HBASE-7215
> URL: https://issues.apache.org/jira/browse/HBASE-7215
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Blocker
> Fix For: 0.96.0
>
> Attachments: 7215-v2.txt, 7215v3_mutableresult.txt, 7215v3.txt,
> 7215v3.txt, 7251-SKETCH.txt, MutableResult.java
>
>
> Making blocker as suggested by Stack.
> At least the following still use Put/Delete as writables.
> * IdentityTableReduce.java
> * MultiPut.java
> * HRegionServer.checkAndMutate
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
