You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Sylvain Wallez (JIRA)" <ji...@apache.org> on 2016/12/22 15:25:58 UTC

[jira] [Created] (CURATOR-369) Improve log format in EnsembleTracker.processConfigData()

Sylvain Wallez created CURATOR-369:
--------------------------------------

             Summary: Improve log format in EnsembleTracker.processConfigData()
                 Key: CURATOR-369
                 URL: https://issues.apache.org/jira/browse/CURATOR-369
             Project: Apache Curator
          Issue Type: Bug
          Components: Framework
    Affects Versions: 3.2.1
            Reporter: Sylvain Wallez
            Priority: Minor


EnsembleFrameworkTracker has a [log statement|https://github.com/apache/curator/blob/CURATOR-3.0/curator-framework/src/main/java/org/apache/curator/framework/imps/EnsembleTracker.java#L182] that doesn't format its value correctly and is adding noise in log files.

I'd like to provide a fix for this by logging the properties object once it's been parsed, but I'm confused about what branch to patch against. This class exists in the CURATOR-3.0 branch, but not in master.

Is creating a PR against the CURATOR-3.0 branch the way to go?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)