[
https://issues.apache.org/jira/browse/ACCUMULO-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782422#comment-13782422
]
Mike Drob edited comment on ACCUMULO-1627 at 9/30/13 11:32 PM:
---------------------------------------------------------------
This makes me think that {{Mutation}} should be an interface with
{{TableMutation}} and {{ConditionalMutation}} implementations. I think the
example from CS classes was that a {{3Dpoint}} and a {{2Dpoint}} are both
different kinds of {{Point}} s, and that it is wise to resist the temptation
for {{3DPoint extends 2Dpoint}}, because really, it doesn't.
was (Author: mdrob):
This makes me think that {{Mutation}} should be an interface with
{{TableMutation}} and {{ConditionalMutation}} implementations. I think the
example from CS classes was that a {{3Dpoint}} and a {{2Dpoint}} are both
different kinds of {{Point}}s, and that it is wise to resist the temptation for
{{3DPoint extends 2Dpoint}}, because really, it doesn't.
> Add hashcode() and equals() to ConditionalMutation
> --------------------------------------------------
>
> Key: ACCUMULO-1627
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1627
> Project: Accumulo
> Issue Type: Sub-task
> Components: client, tserver
> Reporter: Keith Turner
> Assignee: Bill Havanki
> Labels: newbie
> Fix For: 1.6.0
>
>
> ConditionalMutation should define equals() and hashcode() methods that
> consider the conditions. Its parent class defines those methods, so it
> should.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
