Member since
09-29-2015
871
Posts
723
Kudos Received
255
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
4058 | 12-03-2018 02:26 PM | |
3042 | 10-16-2018 01:37 PM | |
4179 | 10-03-2018 06:34 PM | |
3022 | 09-05-2018 07:44 PM | |
2288 | 09-05-2018 07:31 PM |
09-19-2017
02:09 PM
@sally sally By setting your minimums (Min Num Entries and Min Group Size to some large value), FlowFiles that are added to a bin will not qualify for merging right away. You should then set "Max Bin Age" to a unit of time you are willing to allow a bin to hang around before it is merged regardless of the number of entries in that bin or that bins size. As far as the number of bins go, a new bin will be created for each unique filename found in the incoming queue. Should the MergeContent processor encounter more unique filenames then there are bins, the MergeContent processor will force merging of the oldest bin to free a bin for the new filename. So it is important to have enough bins to accommodate the number of unique filenames you expect to pass through this processor during the configured "max bin age" duration; otherwise, you could still end up with 1 FlowFile per merge. Thanks, Matt
... View more
09-20-2017
01:33 PM
If you want to have a default value of "null" then the type of your field needs to be a union of null and the real type. For example, for timestamp you would need: "type": ["long", "null"]
... View more
09-05-2017
04:36 AM
I found my problem, using ${event_type} in the Correlation Attribute Name where it should just be event_type. All is sorted now thanks a lot for the help!
... View more
09-01-2017
04:56 PM
Issue was browser version related. Switching to a newer version of the browser resolved this issue.
... View more
08-29-2017
01:17 PM
Unfortunately it depends on the processor, some processors were implemented to support '\\n' and some were not. Usually the documentation for the given property will say how to enter the value.
... View more
02-14-2018
02:40 PM
1 Kudo
@Bryan Bende & @Greg Keys the error seems to persist with HDF 3.0.2. Are there any news on a workaround or a fix?
... View more
04-03-2019
04:42 PM
@Bryan Bende : I have a workflow like HandleHttpRequest -> InvokeHttp -> Custom Processor -> HandleHttpResponse. My requirement is that I want to support multiple templated jsons and URL sent to HandleHttpRequest will have query params who values should replace some values in the templated jsons based on the template I need. These templated jsons are nested and complex in structure. Pleaseee suggest how to do this. Different posts mention about diff processors like EvaluateJsonPath, ReplaceText, UpdateAttribute and so on but which processor should I use to store my templated json and how can I do the values replacement. I am new to NiFi and request your help on this and I am basically from Java background.
... View more
08-08-2017
03:59 PM
Yes, ( right-click , download or clear ) is what i am doing currently. But we cannot have this manual dependency in production env right.? thats why i was checking to see if there is any better way. We are planning to migrate to HDF 3.0 soon , hopefully it works.
... View more
07-12-2017
03:12 PM
Thank you very much Bryan! Now, I am able to lookup the attribute and get the value for that key. But, I am still confused on how the "Result RecordPath" works. This is how I have configured my Lookup Service: But, when I am done with the lookup and check out DataProvenance, I do not see any field or attribute called "token". The value that is returned by the lookup now goes into a new attribute "key" (which now has a value "def". I was intending the value to go to "token" attribute. How do I do that?
I have also attached my process flow XML (test-lookupattribute.xml). Can you point me to any other documentation (if any) other than the Usage documents to figure out exactly how to use the LookupXXXXService processors? Thanks! VJ
... View more