[ https://issues.apache.org/jira/browse/STORM-2854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jungtaek Lim resolved STORM-2854. --------------------------------- Resolution: Fixed Fix Version/s: 1.2.0 2.0.0 Merged into master and 1.x branch. > Expose IEventLogger to make event logging pluggable > --------------------------------------------------- > > Key: STORM-2854 > URL: https://issues.apache.org/jira/browse/STORM-2854 > Project: Apache Storm > Issue Type: Improvement > Components: storm-client > Reporter: Jungtaek Lim > Assignee: Jungtaek Lim > Labels: pull-request-available > Fix For: 2.0.0, 1.2.0 > > Time Spent: 3h 20m > Remaining Estimate: 0h > > For the first time, "Event Logger" feature is designed to make implementation > pluggable, so that's why IEventLogger exists, but we didn't have actual use > case other than just writing them to the file at that time, so we just > simplified the case. > Now we have use case which also write events to file, but with awareness of > structure of event so that it can be easily parseable from log feeder. We > would want to have custom IEventLogger to represent event as our own format > in this case. > There's another issue as well: EventInfo has `ts` which stores epoch but it's > defined as String, not long. -- This message was sent by Atlassian JIRA (v6.4.14#64029)