nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthew Burgess <>
Subject Re: control nifi processors with REST (ie without GUI)
Date Tue, 19 Jan 2016 16:57:31 GMT
I have seen this too, IIRC it is due to an out-of-date “revision” value in the PUT.  Try
getting the most recent revision number (GET /controller/revision) and putting that in the
body of the PUT.

If you have already done that, the other thing I think that causes this response is the wrong
mime type, should be "application/x-www-form-urlencoded”.

Hope this helps!  Regards,

From:  <>
Reply-To:  <>
Date:  Tuesday, January 19, 2016 at 11:48 AM
To:  "" <>
Subject:  control nifi processors with REST (ie without GUI) 


My  nifi version  :  nifi 0.4.1


I try to control a nifi topology with REST API  (java  jaxRS client ).

I  have a Nifi group of 2 processors and I can retrieve the  json config for each of them
.  perfect !

But when  I modify the json config ( Input Directory for my  getfile processor instance) and
 use REST PUT API to update  the proc config, 

I get back these messages :


: HTTP status code : 409

: This NiFi instance has been updated by 'anonymous'. Please refresh to synchronize the view.



And the config of the processor is not updated  ( checking it with GUI, doing a manual refresh
status  and also a REST get) 

Any idea ?  problem of user auth?


Best regards 






Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees
et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par
erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant
susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may
be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message
and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed
or falsified.
Thank you.

View raw message