[
https://issues.apache.org/jira/browse/KUDU-2009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010737#comment-16010737
]
Will Berkeley commented on KUDU-2009:
-------------------------------------
That post is very dated now. We should probably write new documentation for the
Kudu Flume Sink, especially since its capabilities have expanded a lot with a
couple of newer OperationsProducer implementations.
> Update of Flume Kudu Sink documentation (Impala table names and sink class
> names)
> ---------------------------------------------------------------------------------
>
> Key: KUDU-2009
> URL: https://issues.apache.org/jira/browse/KUDU-2009
> Project: Kudu
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 1.4.0
> Reporter: David Hamilton
> Priority: Minor
>
> Nice documentation exists for using the Flume Kudu Sink at:
> https://kudu.apache.org/2016/08/31/intro-flume-kudu-sink.html
> Two updates could be made, however, regarding the steps for creating a Flume
> configuration file (to improve clarity for Impala users and also update sink
> / producer class names to match their names in 1.4.0-SNAPSHOT):
> 1) Include a note that the Kudu table name, if created by Impala may take
> the form of impala::<impala_db_name>.<impala_table_name> - i.e.
> Change from: {code}agent1.sinks.sink1.tableName = stats{code}
> Change to: {code}agent1.sinks.sink1.tableName = impala::default.stats{code}
> 2) Update the class names of the sink type and sink producer:
> Change from: {code}agent1.sinks.sink1.type =
> org.apache.flume.sink.kudu.KuduSink{code}
> Change to:
> {code}agent1.sinks.sink1.type=org.apache.kudu.flume.sink.KuduSink{code}
> Change from: {code}agent1.sinks.sink1.producer =
> org.apache.kudu.flume.sink.SimpleKuduEventProducer{code}
> Change to:
> {code}agent1.sinks.sink1.producer=org.apache.kudu.flume.sink.SimpleKuduOperationsProducer{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
