MemoryChannel should push events back into channel on rollback
--------------------------------------------------------------
Key: FLUME-772
URL: https://issues.apache.org/jira/browse/FLUME-772
Project: Flume
Issue Type: Improvement
Affects Versions: NG
Reporter: E. Sammer
Priority: Blocker
Currently the MemoryChannel (i.e. the "best effort" channel) transaction
provider drops events if the consumer rolls back. In other words a sink that
does:
{code}
tx = channel.getTransaction()
event = channel.take()
tx.rollback()
{code}
...loses the event. Instead, the event should be pushed back into the channel
so it's redelivered. Ideally, it should be inserted at the end of the channel
to be as close to totally ordered as possible. There is the question of what to
do if the channel is at capacity.
--
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
