[
https://issues.apache.org/jira/browse/IGNITE-8935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533968#comment-16533968
]
ASF GitHub Bot commented on IGNITE-8935:
----------------------------------------
GitHub user alamar opened a pull request:
https://github.com/apache/ignite/pull/4318
IGNITE-8935 toString() or exclusion for most classes accessible from
IgniteConfiguration
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8935
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4318.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4318
----
commit 2c664b7be5cce57f5e5e1ecb97705f372632c36a
Author: Ilya Kasnacheev <ilya.kasnacheev@...>
Date: 2018-07-05T17:52:51Z
IGNITE-8935 toString() or exclusion for most classes accessible from
IgniteConfiguration.
----
> IgniteConfiguration dependents should have toString
> ---------------------------------------------------
>
> Key: IGNITE-8935
> URL: https://issues.apache.org/jira/browse/IGNITE-8935
> Project: Ignite
> Issue Type: Improvement
> Affects Versions: 2.5
> Reporter: Ilya Kasnacheev
> Assignee: Ilya Kasnacheev
> Priority: Minor
> Labels: usability
>
> Ignite configuration is printed on startup, but some classes which are
> usually referred do not have toString() implemented, leading to gems such as
> connectorCfg=org.apache.ignite.configuration.ConnectorConfiguration@7d8704ef
> Those classes should have toString implemented which will conform to
> https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines#CodingGuidelines-StringOutput
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
