-on-the-fly-for-many-sensor-devices-tp47p540.html
Sent from the Apache NiFi Users List mailing list archive at Nabble.com.
t to close them).
>
> I've logged most of the issues I encountered on Andrew's github repo.
>
>
>
>
>
> --
> View this message in context: http://apache-nifi-users-list.
> 2361937.n4.nabble.com/Re-Processors-on-the-fly-for-
> many-sensor-devices-tp47p466.html
> Sent f
restart to close them).
I've logged most of the issues I encountered on Andrew's github repo.
--
View this message in context:
http://apache-nifi-users-list.2361937.n4.nabble.com/Re-Processors-on-the-fly-for-many-sensor-devices-tp47p466.html
Sent from the Apache NiFi Users List mailing list archive
.
--
View this message in context:
http://apache-nifi-users-list.2361937.n4.nabble.com/Re-Processors-on-the-fly-for-many-sensor-devices-tp47p427.html
Sent from the Apache NiFi Users List mailing list archive at Nabble.com.
Good morning Davy,
I have all (barring tests that fail) code in place to fulfill NIFI-2615
[1]. I plan on wrapping up the testing of it today and submitting a P/R.
One thing to call out is that at present it is it's own module. However, I
plan on adding it to the NiFi Standard Processor bundle
Hi Davy,
Thanks for the P/R - I merged that in just a little bit ago.
I think the feature you are describing makes total sense, I'm sure this
would be useful in many different use cases. I am in the process of
wrapping up the changes to fulfill JIRA NIFI-2615 [1]. Do you want to add
the
Hi Andrew,
We'd be happy to test and provide feedback.
We have a use-case now with Nifi that we're in the process of implementing.
If you have sources or binaries feel free to let me know.
Regards,
Davy
On Fri, Sep 30, 2016 at 9:24 PM, Andrew Psaltis
wrote:
> Hi
Hi Andrew,
We tested your 0.0.6 binary and it seemed to do what we want.
Unfortunately it is not compatible with the current Nifi version.
Do you have a binary available that would work with nifi 1.0.0 ?
Thx.
On Wed, Sep 28, 2016 at 11:39 PM, Andrew Psaltis
wrote:
>
Davy,
The processor I have been working on may meet your needs. You are correct,
at this time I have not pushed the source for it, still working through
some hurdles. The one thing to work out is how you would dynamically add
the processors -- suppose you may be able to use the REST API for NiFi.
Just wanted to clarify something about ListenTCP... it does support
multiple incoming connections, however if you using the batch output
capability, one flow file will contain data across all the connections.
I do agree with Andrew that based on the description it sounds like NiFi is
expected to
Correct... But I don't think that one is in the official nifi distribution.
I did stumble upon your repo / jira issue. (The repo didn't contain any
sources, only binaries I think).
But I guess there we would also need some way of dynamically adding these
processors (as it would require 1
Hi,
Thanks for the response ... it's an existing network of sensors. The
sensors spit out data over a serial interface that is exposed over a tcp
connection. (rs232 -> ethernet converter in the sensor).
The current sensor architecture involves clients making direct connections
to the individual
Hello
Can you talk a bit about why you'd want ListenTCP processors tied to a
given sensor? You should be able to have many sensors to a single
ListenTCP. Each stream will be between a source/sensor and nifi so
data won't be getting intermingled there. If we're not providing
enough
We have a large number of sensors that send out data via TCP. The idea is
to use a ListenTCP processor in Nifi to capture the data, do some filtering
/ basic transformation before sending it upstream into our stack.
We can configure individual ListenTCP processors for each sensor, and that
works
14 matches
Mail list logo