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

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.2.1
• Fix Version/s: 3.3.0
• Component/s: Framework
• Assignee: Jordan Zimmerman
• Reporter: Sylvain Wallez
• Created: 22/Dec/16 15:25
• Updated: 28/Dec/16 17:42
• Resolved: 28/Dec/16 17:42

Description

EnsembleFrameworkTracker has a log statement that doesn't format its value correctly and is adding noise in log files.

Sample output of this statement is as follows:

[2016-12-09 12:16:26,046][INFO ][org.apache.curator.framework.imps.EnsembleTracker][] New config event received: [115, 101, 114, 118, 101, 114, 46, 49, 48, 61, 108, 111, 99, 97, 108, 104, 111, 115, 116, 58, 50, 56, 57, 56, 58, 51, 56, 57, 56, 58, 112, 97, 114, 116, 105, 99, 105, 112, 97, 110, 116, 59, 48, 46, 48, 46, 48, 46, 48, 58, 50, 49, 57, 49, 10, 118, 101, 114, 115, 105, 111, 110, 61, 49, 48, 48, 48, 48, 48, 48, 48, 48]

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?

Issue Links

• links to: GitHub Pull Request #179