[
https://issues.apache.org/jira/browse/IGNITE-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16744059#comment-16744059
]
Andrey Kalinin commented on IGNITE-3622:
----------------------------------------
[~vozerov] I would like to know your opinion about the presence of idHash in
the toString() method output. Can it be safely removed?
> BinaryObject: print idHash in toString() method only in debug mode
> ------------------------------------------------------------------
>
> Key: IGNITE-3622
> URL: https://issues.apache.org/jira/browse/IGNITE-3622
> Project: Ignite
> Issue Type: Task
> Components: binary
> Affects Versions: 1.6
> Reporter: Alexey Kuznetsov
> Assignee: Rohit Mohta
> Priority: Trivial
> Labels: newbie
>
> Current implementation of BinaryObject.toString() method print idHash for
> internal objects, for example, for AffinityKey.
> This lead to "unstable" result of toString() method, you will get different
> strings on each toString() invocation.
> Possible fix: introduce
> {code}
> private static final boolean debug = false;
> {code}
> And check this flag in toString().
> If some one will need idHash for debug reasons he could change this flag in
> its private build and debug.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
