[
https://issues.apache.org/jira/browse/FLUME-896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13190009#comment-13190009
]
Peter Newcomb commented on FLUME-896:
-------------------------------------
Sorry, I didn't mean to offend. I was trying to follow the instructions on the
how-to-contribute[1] page, but failed to recognize the difference between
assigning a JIRA to myself and REassigning a JIRA to myself.
I did attempt to describe what I was doing as early as I could in the comments
above (though I'm sure I could have done better), but as I was primarily
focused on meeting an internal deadline I could not wait to write code until
after public discussion. I'm perfectly OK with my code and even approach to be
rejected as either inadequate or simply not desired, but wanted to share in
case it was useful. I'm also happy to shelve this and join in discussion on a
FEP on the subject as you suggest.
Anyway, the code I posted does actually guarantee sequential access, though
some interleaving may occur if there are multiple sinks reading from the
channel simultaneously.
-peter
[1] https://cwiki.apache.org/FLUME/how-to-contribute.html
> Implement file write ahead log channel
> --------------------------------------
>
> Key: FLUME-896
> URL: https://issues.apache.org/jira/browse/FLUME-896
> Project: Flume
> Issue Type: New Feature
> Components: Channel
> Affects Versions: NG alpha 1
> Reporter: E. Sammer
> Assignee: Peter Newcomb
> Fix For: v1.1.0
>
>
> Implement a channel that uses a regular file system and a write ahead log for
> durable event delivery.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
