You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Rohit Mohta (JIRA)" <ji...@apache.org> on 2016/12/15 15:12:58 UTC
[jira] [Assigned] (IGNITE-3622) BinaryObject: print idHash in
toString() method only in debug mode
[ https://issues.apache.org/jira/browse/IGNITE-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohit Mohta reassigned IGNITE-3622:
-----------------------------------
Assignee: Rohit Mohta
> 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: newbie
> Affects Versions: 1.6
> Reporter: Alexey Kuznetsov
> Assignee: Rohit Mohta
> Priority: Trivial
> Fix For: 2.0
>
>
> 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
(v6.3.4#6332)