[
https://issues.apache.org/jira/browse/FLUME-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13154742#comment-13154742
]
E. Sammer commented on FLUME-851:
---------------------------------
Praveen:
I agree this is a great feature. It should be possible to write a Channel
implementation that has a priority comparator (or a similar implementation)
that uses the timestamp in the event headers. Currently, we don't guarantee
that all events have a timestamp header, but it's early enough in NG's life
that we could make it true (or simply add System.currentTimeInMillis() on
Channel#put(Event) if the header doesn't exist). We could also add the notion
of an Event TTL (i.e. discard this even if it can't delivered within X millis)
as another way of achieving something similar. Can you describe the ideal
behavior vs. what you've already implemented, if anything, so we can plan out
what this might look like?
Thanks!
> Scribe style of handling events especially when there is a large event
> backlog built-up
> ---------------------------------------------------------------------------------------
>
> Key: FLUME-851
> URL: https://issues.apache.org/jira/browse/FLUME-851
> Project: Flume
> Issue Type: Improvement
> Components: Channel, Node
> Affects Versions: NG alpha 1
> Environment: All
> Reporter: Praveen Ramachandra
>
> Newer events are of much higher value to be delivered than old events that
> have been accumulated.
> Scribe does this very well and would like to incorporate it in flume-ng.
> Currently we use a dirty hack to realize this important/critical feature. If
> this is incorporated in the platform, users of flume-ng will benefit from
> this immensly
--
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
