[
https://issues.apache.org/jira/browse/MESOS-2487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361314#comment-14361314
]
Alexander Rukletsov commented on MESOS-2487:
--------------------------------------------
I wonder whether a single comparison operation is enough. We definitely need a
notion of equivalence, I think that maps to what Michael calls essential
fields. But do we need equality in terms of, say, raw bytes equality? Anyway,
it looks like we can't avoid writing custom equivalence test functions for our
messages.
> Ensure protobuf "==" operator does not go out of sync with new protobuf fields
> ------------------------------------------------------------------------------
>
> Key: MESOS-2487
> URL: https://issues.apache.org/jira/browse/MESOS-2487
> Project: Mesos
> Issue Type: Task
> Reporter: Vinod Kone
>
> Currently when a new field is added to a protobuf that has a custom "=="
> operator defined, we don't make sure that the field is accounted for in the
> comparison. Ideally we should catch such errors at build time or 'make check'
> time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
