Joe:
Thanks, I did number one today and it worked great. I sent it a 700
meg file and it
just kept the first 10 lines.
Thank You.
Leslie Hartman
Joe Percivall wrote:
For number one, you can also use RouteText[1] with the matching strategy "Satisfies Expression". Then as a dynamic
property use this expression "${lineNo:le(10)}". This will route first 10 lines to the "matched" relationship
(assuming "Route to each matching Property Name" is not selected). This option also allows you to route those unmatched
lines elsewhere if you need (if not just auto-terminate the "unmatched" relationship).
The for number two, instead of ReplaceText, you could also use RouteText. Set the matching strategy to "Matches Regular Expression". Then set the dynamic property to match everything and end with "unambiguously" (an example being "((\w|\W)*unambiguously)"). This will route all the text that matches the Regex apart from the end of the file and gives you the option to route the ending text differently if needed.
[1]
https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.RouteText/index.html
Joe- - - - - -
Joseph Percivall
linkedin.com/in/Percivall
e: [email protected]
On Sunday, June 5, 2016 4:41 AM, Leslie Hartman <[email protected]> wrote:
Matthew:
The modifyBytes processor would be the best if it would allow
one to
specify the bytes to keep. I could calculate the number of bytes to
delete,
but when I try and place a variable in the End Offset it says it is
not in the
<Data Size> <Data Unit> format.
As for SegmentContent and SplitText I have tried both of these.
The problem
is that it just takes the original file a splits it in to a bunch of
little files. So if I wanted
say 256 Bytes of a 30 meg file, after running out of memory it would
give me
125 Million 829 Thousand 119 Files to get rid of.
For the 2nd case ReplaceText should work, I'm just having
problems getting
the correct syntax. If someone could provide an example of the
correct syntax
I would appreciate it.
Thank You.
Leslie Hartman
Matthew Clarke wrote:
You may also want to look at using the modifyBytes processor for number 1.
On Jun 4, 2016 1:49 PM, "Thad Guidry" <[email protected]> wrote:
For your 1st case, you can use either SegmentContent by your 256 bytes (or
perhaps you can even use SplitText)
https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.SegmentContent/index.html
https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.SplitText/index.html
For your 2nd case, you can use ReplaceText
https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.ReplaceText/index.html
Thad
+ThadGuidry
