Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
Flume >> mail # user >> "single source - multi channel" scenario  and applying interceptor while writing to only one channel and not on others...possible approaches


Copy link to this message
-
"single source - multi channel" scenario  and applying interceptor while writing to only one channel and not on others...possible approaches
Hi

We have a use case in which
1. spooling source reads data.
2. It needs to write events into multiple channels. It should apply
interceptor only when putting into one channel and should put
the event as it is while putting into another channel.

Possible approach we have thought:

1. Create  2 different sources and then apply interceptor on one and dont
apply on other. But that duplicates reads and increases IO.

Is there any better way of achieving this use case?

Regards,
Jagadish
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB