If it is to drop all events, then it simply returns an empty list. If an interceptor needs to drop events, it just does not return that event in the list that it returns.
The list of events returned by one interceptor is passed to the next interceptor in the chain. The order in which the interceptors are specified is the order in which they are invoked. Interceptors are specified as a whitespace separated list in the source configuration. This is made possible through by specifying the list of interceptor builder class names in the configuration. An interceptor can modify or even drop events based on any criteria chosen by the developer of the interceptor.
Interceptors are classes that implement .Interceptor interface. This is done with the help of interceptors. A Flume agent is a (JVM) process that hosts the components through which events flow from an external source to the next destination (hop).įlume has the capability to modify/drop events in-flight. Send event to selected sink (here is sink polling pull)Ī Flume event is defined as a unit of data flow having a byte payload and an optional set of string attributes.Enter the sink selector and select sink according to the configuration policy.Send the event to the selected channel cache (source push here).Enter the channel selector and select the channel according to the configuration policy.Then, through the interceptor chain, the even set is chained (modified or discarded).Source reads the data source and encapsulates it into event (process method).Quick development of custom components, refer to.Parameter specifications are unfamiliar when defining components, such as specifying the parameter configuration of source.Quickly get familiar with the specific type of a component, such as how to select the source.
Introduction to flume user guide page Superior menuas well as Menu on this page, which can be quickly located according to requirements (see Appendix 1).
0 kommentar(er)
