If you do a GET for that processor the response will contain the current revision (clientId + version). When you submit a mutable request, you must have the most up to date revision version, or have the same clientId that successfully made the last modification. This ensures that a given client is working with the latest version of that component while still supporting asynchronous requests.
Matt On Wed, Feb 8, 2017 at 9:22 AM, maykiwogno <[email protected]> wrote: > I received new error > > Node localhost:9443 is unable to fulfill this request due to: [6, > f35559c1-0dd3-4009-af0f-26fceaa0ec72, b0c63454-89a8-15ef-be22- > 959bd4a72e5a] > is not the most up-to-date revision. This component appears to have been > modified > > {"revision":{"clientId":"f35559c1-0dd3-4009-af0f- > 26fceaa0ec72","version":6},"component":{"id":"b0c63454- > 89a8-15ef-be22-959bd4a72e5a","state":"STOPPED"}} > > i've used uuidgen to generate clientID > > > > -- > View this message in context: http://apache-nifi-developer- > list.39713.n7.nabble.com/How-restart-and-clear-state-for- > listHDFS-processor-tp14616p14625.html > Sent from the Apache NiFi Developer List mailing list archive at > Nabble.com. >
