THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
2. Configure the Sink within your Agent similar to the example below and kick off flume.
Code Block |
---|
########################################################################
################## SINK CONFIGURATION ##################################
########################################################################
# FQCN (Fully-qualified class name) component type for the type
octopus.sinks.solr1.type = org.apache.flume.sink.solr.SolrSink
# Channel for this sink
octopus.sinks.solr1.channel = c1
octopus.sinks.solr1.serverUrl = http://localhost:8983/solr/flume
# Number of events to be written per transaction
octopus.sinks.solr1.batchSize = 500
# The number of background worker threads used by ConcurrentUpdateSolrServer to empty the queue
octopus.sinks.solr1.threadCount = 2
# Serializes the headers and body of an event into SolrInputDocuments that are sent to Apache Solr
octopus.sinks.solr1.serializer = org.apache.flume.sink.solr.SolrBasicEventSerializer
# A comma-delimited list of headers allowed.
# These must also be valid field names in the schema for this index
octopus.sinks.solr1.serializer.validHeaderFields = loglevel,timestamp,hostname
# The name of the field in the schema used for the event body. 'body' by default.
octopus.sinks.solr1.serializer.bodyFieldname = body
|