[
https://issues.apache.org/jira/browse/KAFKA-17015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17856752#comment-17856752
]
Chia-Ping Tsai commented on KAFKA-17015:
----------------------------------------
Normally, we should implements both `equal` and `hashcode`. However, the
`equal` is used for testing only, and so we don't expect that hashcode should
gets used.
> ContextualRecord#hashCode()、ProcessorRecordContext#hashCode() Should not be
> deprecated and throw an exception
> -------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-17015
> URL: https://issues.apache.org/jira/browse/KAFKA-17015
> Project: Kafka
> Issue Type: Improvement
> Reporter: dujian0068
> Assignee: dujian0068
> Priority: Minor
>
> when review PR#16970。 I find function
> `ContextualRecord#hashCode()、ProcessorRecordContext#hashCode() ` be
> deprecated because they have a mutable attribute, which will cause the
> hashCode to change。
> I don't think that hashCode should be discarded just because it is mutable.
> HashCode is a very important property of an object. It just shouldn't be used
> for hash addressing, like ArayList
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
