[
https://issues.apache.org/jira/browse/IGNITE-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Kuznetsov updated IGNITE-3622:
-------------------------------------
Description:
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.
was:
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
private static final boolean debug = false;
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.
> 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
> Affects Versions: 1.6
> Reporter: Alexey Kuznetsov
> Priority: Minor
> Fix For: 1.8
>
>
> 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)
