Mailing-List: contact user-help@flume.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@flume.apache.org
From: "Keane, Mike" <mkeane@conversantmedia.com>
To: "user@flume.apache.org" <user@flume.apache.org>
Subject: RE: Spooldir needs a Kafka topic defined in the agent.conf
Thread-Topic: Spooldir needs a Kafka topic defined in the agent.conf
Thread-Index: DBkj148gtQYrZWQrOFM5ip702QtXAPBJoFki8CQ6PDWP3Rvlcg==
Date: Thu, 7 Jan 2016 14:03:54 +0000
Message-ID: 
 <FECC20AA497E824FB5029C825E38837CE8318A93@ORD-EXDB101.corp.valueclick.com>
References: <450422392.14419810.1452098035518.JavaMail.zimbra@plista.com>
 <FECC20AA497E824FB5029C825E38837CE83181A4@ORD-EXDB101.corp.valueclick.com>,<1419516952.14647459.1452171138227.JavaMail.zimbra@plista.com>
In-Reply-To: <1419516952.14647459.1452171138227.JavaMail.zimbra@plista.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

I assume you want to the topic header based on the contents of the line of =
data read in from the Spooling Directory Source?  If so I think you want to=
 configure a Regex Extract Interceptor, or implement your own interceptor t=
o do this.  =


http://flume.apache.org/FlumeUserGuide.html#regex-extractor-interceptor


________________________________________
From: Simone Roselli [simone.roselli@plista.com]
Sent: Thursday, January 07, 2016 6:52 AM
To: user
Subject: Re: Spooldir needs a Kafka topic defined in the agent.conf

Hi,

in your configuration you define the topic name in the agent.conf (spooling=
Agent.sinks.kafka-sink-1.topic =3D data_in);

This is what I do not want.

I would like the spoolDir to retrieve the topic name from the event headers


Simone Roselli
ITE Sysadmin
simone.roselli@plista.com
http://www.plista.com

----- Original Message -----
From: "Keane, Mike" <mkeane@conversantmedia.com>
To: "user" <user@flume.apache.org>
Sent: Wednesday, January 6, 2016 6:30:41 PM
Subject: RE: Spooldir needs a Kafka topic defined in the agent.conf

I attempted to put together a little Flume+Kafka tutorial including using C=
amus to run map-reduce jobs pulling from Kafka and writing to HDFS.  My exa=
mple uses a spoolDirSource, KafkaChannel & KafkaSink.  This may be of some =
help to you.

https://github.com/mbkeane/BigDataTechCon/blob/master/README.md


________________________________________
From: Simone Roselli [simone.roselli@plista.com]
Sent: Wednesday, January 06, 2016 10:33 AM
To: user@flume.apache.org
Subject: Spooldir needs a Kafka topic defined in the agent.conf

Hi,

I'm having trouble configuring a spooldir source using the Kafka sink

In Flume-NG I can use the Kafka sink without specify a topic name in the ag=
ent.conf, since the event contains this topic name in the headers.

Things look different using the spooldir source. If you don't provide a top=
ic name in agent.conf, it will only try a default one (default-flume-topic).

Is there a way to force spooldir source using the topic name in the headers?

ps: I'm using Spooldir with the AVRO deserialization; no other particular c=
onfiguration. "fileHeader" is set as "true"


Many thanks


Simone Roselli
ITE Sysadmin
simone.roselli@plista.com
http://www.plista.com


This email and any files included with it may contain privileged,
proprietary and/or confidential information that is for the sole use
of the intended recipient(s).  Any disclosure, copying, distribution,
posting, or use of the information contained in or attached to this
email is prohibited unless permitted by the sender.  If you have
received this email in error, please immediately notify the sender
via return email, telephone, or fax and destroy this original transmission
and its included files without reading or saving it in any manner.
Thank you.


This email and any files included with it may contain privileged,
proprietary and/or confidential information that is for the sole use
of the intended recipient(s).  Any disclosure, copying, distribution,
posting, or use of the information contained in or attached to this
email is prohibited unless permitted by the sender.  If you have
received this email in error, please immediately notify the sender
via return email, telephone, or fax and destroy this original transmission
and its included files without reading or saving it in any manner.
Thank you.