Hi All!
I have to implement a flow with NiFi that involves consuming different AMQP
queues whose number may change in time.
One of the requirements is that when a new queue is available (of an old one is
no more available) the NiFi flow adjusts to the new situation without the need
for any manual adjustments.
In order to implement this I thought of having a simple configuration table in
a postgres DB, listing the names of the active queues (that an operator would
update when needed), and then use NiFi to go check periodically the queue names
list and feed it parametrically to a single ConsumeAMQP processor.
However, I realized that my plan is not applicable because:
1. ConsumeAMQP does not allow incoming relationships
2. Its "Queue" property does not allow values in Expression Language (so
putting a variable value like ${queue_name} wouldn't work, right?)
Do you have an alternative, doable approach in NiFi to suggest me?
Thank you very much,
Luca
Luca Giovannini
Information Systems Analyst
Dedagroup Public Services
www.linkedin.com/in/lucagio/<http://www.linkedin.com/in/lucagio/>
T +39.051.278.928 | M +39.347.799.3183 | VoIP 951.128
Dedagroup Public Services Srl - Sede di Casalecchio di Reno, Via del Lavoro 67
www.dedagroup.it/public-services<http://www.dedagroup.it/public-services>
[cid:[email protected]]<http://www.dedagroup.it/home>
Le informazioni contenute in questo messaggio di posta elettronica sono
riservate e confidenziali e ne e' vietata la diffusione in qualsiasi modo o
forma. Qualora Lei non fosse la persona destinataria del presente messaggio, La
invitiamo a non diffonderlo e ad eliminarlo, dandone gentilmente comunicazione
al mittente.
The information included in this e-mail and any attachments are confidential
and may also be privileged. If you are not the correct recipient, you are
kindly requested to notify the sender immediately, to cancel it and not to
disclose the contents to any other person.
