I'm not sure if this what you are looking for, but here is an example flow that generates data like: A,B,C,D 1;2;3;4 It then splits it into two lines, routes the first line to an ExtractText setup to parse with commas, and routes the second line to a different ExtractText to parse semi-colons. routeextractdelimitedtext.xml ... View more

There isn't a specific processor that is made just for parsing delimited lines, mostly because you can do that with ExtractText already. You should only need one pattern to parse the whole line, lets say I have a simple CSV with 4 columns, you could have one property like this: csv = (.+),(.+),(.+),(.+) That will add attributes csv.1, csv.2, csv.3, csv.4 containing each respective column. You could have different instances of ExtractText to handle the different types of delimiters, would need to route the data to each appropriately. For a more user friendly option you could implement a custom processor like ParseCSV or ParseDelimited where you had a property to take the delimiter and then used some kind of parsing library, or your own code, to parse the line. A second alternative is to write a Groovy or Jython script to do the parsing and use the ExecuteScript processor. ... View more

I think what you suggested makes sense. I am not very familiar with these email processors, but if you are still using ConsueIMAP I think that would be handling getting the new messages and marking them as read, all your script would be doing is receiving a flow file with the message in it and parsing it like ExtractEmailAttachments was doing, but working around the missing headers. ... View more

I had a feeling it was a problem with the output of ConumeIMAP, that JIRA definitely looks like what you are seeing. I'm glad we have already captured the issue, although sorry that it is causing you problems. ... View more

In your flow from the other post you are getting a file from FetchSFTP, then splitting each line with SplitText, then using ExtractText to parse out the values, and ReplaceText to construct a SQL statement. The ExtractText processor is the one that needs to understand the delimiter in order get the value of each column. Since your flow was working you must have already configured ExtractText with a pattern to parse the line right? So are you just asking how to handle more delimiters? ... View more

If it is not sensitive, would you be able to provide an example of the flow file content that is failing? You could get this from using provenance, or from routing the failure of ExtractEmailAttachments to a directory using PutFile. ... View more

What do you want to do with your text files? do you want to convert it to another format, if so what format? There are many existing processors in NiFi that can manipulate text: - ReplaceText can modify the content by finding a pattern and performing a replacement - ExtractText can find patterns and extract them into attributes - SplitText can split the lines of a text file - ExecuteScript can apply a Groovy/Jython script to manipulate the text It really depends what you want to do. ... View more

I think you might be running into this: https://support.mozilla.org/en-US/questions/1058856 You could try going into about:config of Firefox and adding the address into the insecure fallback hosts as that article mentions, or you could also try setting security.tls.version.min to 1.2 to see if it forces using 1.2. I believe NiFi allows any of the TLS versions to be used, and I think when your Firefox negotiates with NiFi it ends up choosing TLSv1, and then Firefox says that is not supported anymore for some reason, at least this is what I am guessing based on the above link. You could also just try Chrome, usually Chrome will prompt you with a warning about being unable to validate the site, which is normal because you are using a self-signed cert, and then you just add exception and continue. For what its worth, Chrome 52 and Firefox 48.0.2 both work for me. ... View more