Re: regex_extractor NOT replacing the HDFS path vaiable

2016-02-18 Thread iain wright
ruary 17, 2016 9:27 PM > > *To:* user@flume.apache.org > *Subject:* Re: regex_extractor NOT replacing the HDFS path vaiable > > > > Hi Sutanu, > > > > This is working out as well: > > > > multi-ale2-station.sources.source1.interceptors.i1.re

RE: regex_extractor NOT replacing the HDFS path vaiable

2016-02-17 Thread Sutanu Das
of the python script output We run Hortonworks and we are on HDP 2.3 – I think it is Flume 1.5 I look forward to your testing, thanks again Ian. From: iain wright [mailto:iainw...@gmail.com<mailto:iainw...@gmail.com>] Sent: Wednesday, February 17, 2016 8:06 PM To: user@flume.apache.org<mai

Re: regex_extractor NOT replacing the HDFS path vaiable

2016-02-17 Thread iain wright
message. > > On Wed, Feb 17, 2016 at 6:18 PM, Sutanu Das wrote: > >> Thanks Ian, >> >> >> >> Here is the s.out which is a text file of the python script output >> >> >> >> We run Hortonworks and we are on HDP 2.3 – I think it is Flum

Re: regex_extractor NOT replacing the HDFS path vaiable

2016-02-17 Thread iain wright
3 – I think it is Flume 1.5 > > > > I look forward to your testing, thanks again Ian. > > > > *From:* iain wright [mailto:iainw...@gmail.com] > *Sent:* Wednesday, February 17, 2016 8:06 PM > > *To:* user@flume.apache.org > *Subject:* Re: regex_extractor NOT rep

RE: regex_extractor NOT replacing the HDFS path vaiable

2016-02-17 Thread Sutanu Das
@flume.apache.org Subject: Re: regex_extractor NOT replacing the HDFS path vaiable Hi Sutanu, Bummer. Its definitely supported, we use it for writing to S3 in the exact manner you intend too. If you want to run this to generate some data as its presented to the source: /usr/local/bin/multi_ale2

Re: regex_extractor NOT replacing the HDFS path vaiable

2016-02-17 Thread iain wright
t; > > *From:* iain wright [mailto:iainw...@gmail.com] > *Sent:* Wednesday, February 17, 2016 7:39 PM > *To:* user@flume.apache.org > *Subject:* Re: regex_extractor NOT replacing the HDFS path vaiable > > > > Config looks sane, > > > > Are events being written &g

RE: regex_extractor NOT replacing the HDFS path vaiable

2016-02-17 Thread Sutanu Das
: user@flume.apache.org Subject: Re: regex_extractor NOT replacing the HDFS path vaiable Config looks sane, Are events being written to /prod/hadoop/smallsite/flume_ingest_ale2//%Y/%m/%d/%H? A couple things that may be worth trying if you haven't yet: - Try host=(ale-\d+-\w+.attwifi.com

Re: regex_extractor NOT replacing the HDFS path vaiable

2016-02-17 Thread iain wright
Config looks sane, Are events being written to /prod/hadoop/smallsite/flume_ ingest_ale2//%Y/%m/%d/%H? A couple things that may be worth trying if you haven't yet: - Try host=(ale-\d+-\w+.attwifi.com) instead of .*host=(ale-\d+-\w+. attwifi.com).* - Try hostname or another header instead of host