Re: IgniteConfiguration, toString(), @GridToStringInclude

2018-07-08 Thread Dmitriy Setrakyan
In that case I would recommend that it is a separate category that can be easily turned off. Also, if there are 1000 caches, then I am certain that they share most of the properties and only a few configuration properties differ. Moreover, it is very likely that most of them belong to the same cach

Re: IgniteConfiguration, toString(), @GridToStringInclude

2018-07-08 Thread Ilya Kasnacheev
Hello! The configuration is usually already present in some other file (in XML or Java form). People who report problems or userlist often fail to provide such file, and they will also definitely forget to provide that other separate file with printed configuation. Log file is our best shot since

Re: IgniteConfiguration, toString(), @GridToStringInclude

2018-07-06 Thread Dmitriy Setrakyan
Can we print out the configuration to a separate file? Moreover, I think we should also print out the configuration differences between nodes, whenever new nodes join topology. D. On Fri, Jul 6, 2018 at 6:51 AM, Ilya Kasnacheev wrote: > Hello! > > I was working on https://issues.apache.org/jira

IgniteConfiguration, toString(), @GridToStringInclude

2018-07-06 Thread Ilya Kasnacheev
Hello! I was working on https://issues.apache.org/jira/browse/IGNITE-8935 to avoid default toString() implementations in classes reachable from IgniteConfiguration, which we print on start-up. I have discovered that by default we avoid printing arrays and collections. We only print those when mar