[jira] Updated: (ZOOKEEPER-222) print C client log message timestamp in human readable form
[ https://issues.apache.org/jira/browse/ZOOKEEPER-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mahadev konar updated ZOOKEEPER-222: Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch Available) I just committed this. thanks pat. print C client log message timestamp in human readable form --- Key: ZOOKEEPER-222 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-222 Project: Zookeeper Issue Type: Improvement Components: c client Affects Versions: 3.0.0 Reporter: Patrick Hunt Assignee: Patrick Hunt Priority: Minor Fix For: 3.1.0 Attachments: ZOOKEEPER-222.patch Noticed this issue during a debugging session -- it's difficult to read/compare the timestamps from the c client. The C client timestamp should be formatted with the same format as the JAVA log timestamps. Note: java uses ISO8601 timestamp formatting by default. Perhaps we should just bit the bullet and move to log4c? Consider this option when addressing this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-222) print C client log message timestamp in human readable form
[ https://issues.apache.org/jira/browse/ZOOKEEPER-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-222: --- Attachment: ZOOKEEPER-222.patch this patch changes the logging format of the c lib to use iso8601 rather than seconds since epoch - makes it a lot easier to compare the c log to the server log (which uses iso8601 by default) print C client log message timestamp in human readable form --- Key: ZOOKEEPER-222 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-222 Project: Zookeeper Issue Type: Improvement Components: c client Affects Versions: 3.0.0 Reporter: Patrick Hunt Priority: Minor Fix For: 3.1.0 Attachments: ZOOKEEPER-222.patch Noticed this issue during a debugging session -- it's difficult to read/compare the timestamps from the c client. The C client timestamp should be formatted with the same format as the JAVA log timestamps. Note: java uses ISO8601 timestamp formatting by default. Perhaps we should just bit the bullet and move to log4c? Consider this option when addressing this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (ZOOKEEPER-222) print C client log message timestamp in human readable form
[ https://issues.apache.org/jira/browse/ZOOKEEPER-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Patrick Hunt updated ZOOKEEPER-222: --- Status: Patch Available (was: Open) print C client log message timestamp in human readable form --- Key: ZOOKEEPER-222 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-222 Project: Zookeeper Issue Type: Improvement Components: c client Affects Versions: 3.0.0 Reporter: Patrick Hunt Assignee: Patrick Hunt Priority: Minor Fix For: 3.1.0 Attachments: ZOOKEEPER-222.patch Noticed this issue during a debugging session -- it's difficult to read/compare the timestamps from the c client. The C client timestamp should be formatted with the same format as the JAVA log timestamps. Note: java uses ISO8601 timestamp formatting by default. Perhaps we should just bit the bullet and move to log4c? Consider this option when addressing this issue. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
