This is the documentation for Cloudera Enterprise 5.8.x. Documentation for other versions is available at Cloudera Documentation.

Flume Morphline Solr Sink Configuration Options

You can use the standard configuration file flume.conf to configure Flume agents, including their sources, sinks, and channels. For more information about flume.conf, see the Flume User Guide.

Flume Morphline SolrSink provides the following configuration options in the flume.conf file:

Property Name	Default	Description
`type`		The FQCN of this class: org.apache.flume.sink.solr. morphline.MorphlineSolrSink
`batchSize`	100	The maximum number of events to take per flume transaction.
`batchDurationMillis`	1000	The maximum duration per Flume transaction (ms). The transaction commits after this duration or when batchSize is exceeded, whichever comes first.
`indexerClass`	org.apache.flume.sink.solr. morphline.MorphlineSolrIndexer	The FQCN of a class implementing org.apache.flume.sink.solr. morphline.SolrIndexer
`morphlineFile`	n/a	The location of the morphline configuration file. In a Cloudera Manager deployment, use: agent.sinks.solrSink. morphlineFile=morphlines.conf In unmanaged deployments, provide the relative or absolute path on the local filesystem to the morphline configuration file. For example: /etc/flume-ng/conf/ tutorialReadAvroContainer.conf
`morphlineId`	null	Name used to identify a morphline if there are multiple morphlines in a morphline configuration file.

This example shows a flume.conf section for a SolrSink for the agent named agent:

agent.sinks.solrSink.type = org.apache.flume.sink.solr.morphline.MorphlineSolrSink
agent.sinks.solrSink.channel = memoryChannel
agent.sinks.solrSink.batchSize = 100
agent.sinks.solrSink.batchDurationMillis = 1000
agent.sinks.solrSink.morphlineFile = /etc/flume-ng/conf/morphline.conf
agent.sinks.solrSink.morphlineId = morphline1

Note: The examples in this document use a Flume MemoryChannel to easily get started. For production use it is often more appropriate to configure a Flume FileChannel instead, which is a high performance transactional persistent queue.

Page generated July 8, 2016.