Member since
06-08-2017
1049
Posts
518
Kudos Received
312
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 11203 | 04-15-2020 05:01 PM | |
| 7102 | 10-15-2019 08:12 PM | |
| 3097 | 10-12-2019 08:29 PM | |
| 11441 | 09-21-2019 10:04 AM | |
| 4322 | 09-19-2019 07:11 AM |
10-12-2017
06:05 PM
@Eric Lloyd, for this case make we cannot mention wild cards like [*] as this processor wont accepting those regex. change FilestoTail property to test[1-2]/[\d|a-z.*]{1,}/test.log Expression Explanation:- test[1-2] --look for test1 or test2 Then property expression check for [\d|a-z.*]{1,} --check for directory name as having digits or letters more than one time and lists all those directories recursively. Configs:- For your case:- Files toTail property should be some thing like below versions/[\d|a-z.*]{1,}/<your-log-file-name>
... View more
10-09-2017
08:13 PM
it is a compress bz2 file and i get an error about the codec when tring to get de new file. INFO compress.CodecPool:
Got brand-new decompressor [.bz2] text: Unable to write to
output stream.
... View more
10-11-2017
11:39 PM
@Sumit Sharma, Use UpdateAttribute processor before PutFile processor with below configurations. Add new property to the processor by clicking + sign filename as ${UUID()} So this will replace the filename of the flowfile to UUID which is unique value all the time, it won't replace the file in your directory.
... View more
10-04-2017
04:58 AM
Thanks Shu
... View more
04-30-2019
05:06 PM
I am facing the same issue right now. My current approach is to have a script to read the first line of all my csv files and then transform the first-line text into create sql statement. I wonder whether this is some built-in solution from HDP.
... View more
11-21-2018
03:45 PM
@Matt Clarke @Shu Thanks for you quick response Matt. Yes you are correct. It's working now. However I did not understood, unless I create a outport in PG1 I am unable to create a connection at root level to another PG2 via outport. Any idea why is that so?
... View more
10-12-2017
02:27 PM
Hi @Shu i ve posted a new question here, hope what i am trying to do in this use case is clear!
... View more
10-02-2017
05:38 AM
Hi @Shu ,yes, your answer is helpful to resolve my problem , thank you very much
... View more
09-26-2017
06:58 PM
Hi @sally sally, if you are extracting only one value to attribute then its easy to use ExtractText processor:- by adding new property to it by adding regex like below. <count>(.*)<\/count> ExtractText Processor configs:- This regex only captures the value in <count></count> message and adds an attribute count to the flowfile.
... View more
09-26-2017
02:53 AM
@sally sally Route on content is to match the contents of ff we cannot compare attribute inside this processor. But we can acheive by using RouteOnAttribute Processor:- as we are having ${message.body} as attribute then add a property ${message.body:contains('<person>')} it will look for message.body attribute contains <person> or not. if yes then it routes to person relation and if ff not having <person> it will routes to unmatched relation. RouteOnContent Processor:- As you are having $message.body as attribute we are not able to use RouteOnContent processor, because it will look the content of ff to find match. E.g:-How RouteOnContent works? Input:- <?xml version="1.0" encoding="UTF-8"?>
<note>
<person>Tove</to>
<from>Jani</from>
<heading>Reminder</heading>
<body>Don't forget me this weekend!</body>
</note> If we are having the above input as the ff content then in Route on content processor we need to give property as It will look for is the content of ff having <person> or not In our case it is yes then it will route to person relation.
... View more