Philippe As far as I know here is the state of affairs for this: 1) You can use EvaluateJSONPath and ReplaceText in a combination for some cases but it is more awkward and difficult than it should be.
2) You can use the execute script processors to write a groovy, javascript, or other type of script to do precisely the manipulation you want on the fly. I think though what we just need to do is finally tackle 'https://issues.apache.org/jira/browse/NIFI-361' and here is a great example to base it on. The work Frank started here 'https://github.com/fsauer65/NiFi-Extensions/tree/master/nifi-jsontransform-bundle' is a great base but we'd need to verify licensing and that the UI elements are license/copyright friendly as well. I believe if you wanted to collaborate/contribute on this one it would be excellent. Thanks Joe On Thu, Apr 7, 2016 at 9:26 AM, <philippe.gib...@orange.com> wrote: > Hello > > I have a DF with a processor owning a json document that need to be > transformed before sent to an ElasticSearch processor > > I have something like this > > $.element.attributes[0].value à not to be changed > > $.element.attributes[0].typeà not to be changed > > … > > $.element.attributes[10].value -> I need to change the value > > $.element.attributes[10].type -> I need to change the type > > … > > …. > > $.element.attributes[15].value à not to be changed > > $.element.attributes[15].typeà not to be changed > > > > > > Its not clear for me what is the right processor to take to implement this > : > > > > EvaluateJsonPath seems nice because I can identify the json path to be > changed but can I replace with it ? > > ReplaceTxt ? seems to be string replace in txt loosing the json structure ? > > > > My requirement is to parse+update the current json on the fly … ( same than > https://github.com/jayway/JsonPath) > > > > Should I need to develop my own processor ? > > > > Any help will be nice J > > Thx > > Philippe > > > > > > _________________________________________________________________________________________________________________________ > > 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.
