Member since
09-11-2015
60
Posts
72
Kudos Received
17
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1674 | 04-11-2017 06:18 PM | |
1345 | 02-21-2017 03:04 PM | |
1900 | 12-28-2016 10:21 PM | |
4396 | 11-30-2016 04:17 AM | |
6188 | 11-08-2016 02:42 PM |
04-11-2017
06:38 PM
The NiFi Spark Receiver itself hasn't needed a true update since before 1.x and the only deps it has is site-to-site[1]. While it would be ideal to upgrade, using the 0.x version of the NiFi Receiver doesn't preclude any blocking features (that I can think of).
[1] https://github.com/apache/nifi/blob/3a7ddc6a35f143c1d4a735226fe7467a83d04583/nifi-external/nifi-spark-receiver/pom.xml
... View more
04-11-2017
06:18 PM
4 Kudos
The NiFi 0.x baseline uses Java 7. The latest of which is NiFi-0.7.2
... View more
02-21-2017
03:04 PM
3 Kudos
Controller Services other than the SSL context are not supported in the 0.1.0 release. I added the functionality to the master branch a little bit ago[1] but there hasn't been a release for it yet. So your best bet is probably to use ListenHttp for now. Where did you see HandleHttpRequest and Response listed as supported in 0.1.0? We should update it to reflect the lack of HttpContextMap support. [1] https://issues.apache.org/jira/browse/MINIFI-154
... View more
12-29-2016
05:28 PM
I don't agree with this answer. All AttributesToJSON would do is wrap the attribute in a JSON object and either put it to another attribute or replace the content. If the user is OK with replacing the content then EvaluateXPath with a destination of "flowfile-content" would be the best. Also it ignores the core question, how to put the value generated by EvaluateXPath to disk.
... View more
12-29-2016
05:19 PM
3 Kudos
It would be much easier if you could set the Destination of EvaluateXPath to "flowfile-content". Are you able to do that?
If so, do that and then you can do "PutFile" to write the content of the FlowFile to the FileSystem.
... View more
12-28-2016
10:21 PM
2 Kudos
I'd suggest checking out the SplitContent processor[1]. Just set "Byte Sequence" to what you want to split it on (','). Then you can process each split as it's own FlowFile. [1] https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.SplitContent/index.html
... View more
12-14-2016
08:37 PM
With the RouteText processor (the destination of that queue) stopped, could you try and change the destination of the connection?
... View more
12-14-2016
03:15 PM
Is this a cluster or standalone instance? This is an odd error that shouldn't be happening so any information about your deployment would be helpful
... View more
12-08-2016
03:21 PM
3 Kudos
Adding on to @Andrew Grande's response. Auto-terminating a relationship does not itself affect scheduling at all. That said, if a FlowFile is routed to certain relationships the processor may yield itself or penalize the FlowFile. For an explanation for "yield" and "penalize" I'd suggest reading the "settings-tab" subsection of the Apache NiFi User guide[1]. For InvokeHttp, when a FlowFile is routed to the failure relationship and the processor is a source processor (no input connections) it will yield itself. If there is an input connection then it will just penalize the FlowFile. [1] https://nifi.apache.org/docs/nifi-docs/html/user-guide.html#settings-tab
... View more