<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>question Re: Multiple properties in EvaluateJsonPath processor in Nifi in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Multiple-properties-in-EvaluateJsonPath-processor-in-Nifi/m-p/192456#M83716</link>
    <description>&lt;P&gt;Can you explain more about your use case? Why do you need to extract ~100 fields, how are they being used downstream? I wonder if a record-based processor or something would be more appropriate...&lt;/P&gt;</description>
    <pubDate>Fri, 21 Sep 2018 10:02:55 GMT</pubDate>
    <dc:creator>mburgess</dc:creator>
    <dc:date>2018-09-21T10:02:55Z</dc:date>
    <item>
      <title>Multiple properties in EvaluateJsonPath processor in Nifi</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Multiple-properties-in-EvaluateJsonPath-processor-in-Nifi/m-p/192454#M83714</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have a big payload coming in from Kafka topic to EvaluateJsonPath Processor in Nifi. I need to extract about 100 fields from the JSON payload that's coming in. I was wondering, if there was a way to specify these fields as property in EvaluateJsonProperty at once instead of specifying them one by one, which is time consuming.&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2018 05:46:32 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Multiple-properties-in-EvaluateJsonPath-processor-in-Nifi/m-p/192454#M83714</guid>
      <dc:creator>krishna_sreeniv</dc:creator>
      <dc:date>2018-09-21T05:46:32Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple properties in EvaluateJsonPath processor in Nifi</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Multiple-properties-in-EvaluateJsonPath-processor-in-Nifi/m-p/192455#M83715</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/97224/krishnasreenivas.html" nodeid="97224"&gt;@Krishna Sreenivas&lt;/A&gt;&lt;/P&gt;&lt;P&gt;As of now there is no built in processor in NiFi that could extract Json attribute dynamically because if we add significant number of attributes dynamically to the flow file, As attributes are hold in &lt;STRONG&gt;memory this will cause performance issues&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;We need to add all the json keys/attributes and matching json path as value in EvaluateJsonPath processor and change the destination property to &lt;STRONG&gt;flowfile-attribute&lt;/STRONG&gt; to keep them as a flow file attributes.&lt;/P&gt;&lt;P&gt;Please refer to &lt;A href="https://community.hortonworks.com/questions/147921/nifi-vectror-addition-in-nifi.html"&gt;This&lt;/A&gt; link for more details regarding dynamic attribute extract processor.&lt;/P&gt;&lt;P&gt;Refer to &lt;A href="https://community.hortonworks.com/questions/142764/how-to-capture-both-key-and-value-of-json-data-wit.html" target="_blank"&gt;this&lt;/A&gt; link regards to similar kind of usecase and end of this thread there is script which you can leverage to extract key/values.&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;If the Answer helped to resolve your issue,&lt;STRONG&gt; Click on Accept button below to accept the answer, &lt;/STRONG&gt;That would be great help to Community users to find solution quickly for these kind of issues.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2018 06:53:42 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Multiple-properties-in-EvaluateJsonPath-processor-in-Nifi/m-p/192455#M83715</guid>
      <dc:creator>Shu_ashu</dc:creator>
      <dc:date>2018-09-21T06:53:42Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple properties in EvaluateJsonPath processor in Nifi</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Multiple-properties-in-EvaluateJsonPath-processor-in-Nifi/m-p/192456#M83716</link>
      <description>&lt;P&gt;Can you explain more about your use case? Why do you need to extract ~100 fields, how are they being used downstream? I wonder if a record-based processor or something would be more appropriate...&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2018 10:02:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Multiple-properties-in-EvaluateJsonPath-processor-in-Nifi/m-p/192456#M83716</guid>
      <dc:creator>mburgess</dc:creator>
      <dc:date>2018-09-21T10:02:55Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple properties in EvaluateJsonPath processor in Nifi</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Multiple-properties-in-EvaluateJsonPath-processor-in-Nifi/m-p/192457#M83717</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/18929/yaswanthmuppireddy.html" nodeid="18929"&gt;@Shu&lt;/A&gt;Thank you very much for pointing me in the right direction. I wrote a script for it.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2018 22:54:10 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Multiple-properties-in-EvaluateJsonPath-processor-in-Nifi/m-p/192457#M83717</guid>
      <dc:creator>krishna_sreeniv</dc:creator>
      <dc:date>2018-09-21T22:54:10Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple properties in EvaluateJsonPath processor in Nifi</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Multiple-properties-in-EvaluateJsonPath-processor-in-Nifi/m-p/192458#M83718</link>
      <description>&lt;P&gt;The 100 fields are to be used by another down stream application. I actually referred to your blog on writing groovy script to extract the fields. But facing issues with that as well.&lt;/P&gt;</description>
      <pubDate>Sat, 22 Sep 2018 02:07:54 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Multiple-properties-in-EvaluateJsonPath-processor-in-Nifi/m-p/192458#M83718</guid>
      <dc:creator>krishna_sreeniv</dc:creator>
      <dc:date>2018-09-22T02:07:54Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple properties in EvaluateJsonPath processor in Nifi</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Multiple-properties-in-EvaluateJsonPath-processor-in-Nifi/m-p/192459#M83719</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/97224/krishnasreenivas.html" nodeid="97224"&gt;@Krishna Sreenivas&lt;/A&gt;&lt;P&gt;Could you add more details regards to your use case for extracting 100 filed values?&lt;/P&gt;&lt;P&gt;If you are extracting the values and &lt;STRONG&gt;preparing csv file&lt;/STRONG&gt; then sending the csv file into Downstream applications? &lt;BR /&gt;if this is the case then &lt;/P&gt;&lt;P&gt; -&amp;gt; if you are using &lt;STRONG&gt;NiFi-1.2+ use &lt;/STRONG&gt;&lt;A href="https://community.hortonworks.com/articles/115311/convert-csv-to-json-avro-xml-using-convertrecord-p.html" target="_blank"&gt;ConvertRecord processor &lt;/A&gt;to convert the &lt;STRONG&gt;Json Format data into CSV format &lt;/STRONG&gt;then send to your down stream systems.&lt;/P&gt;</description>
      <pubDate>Sat, 22 Sep 2018 09:22:49 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Multiple-properties-in-EvaluateJsonPath-processor-in-Nifi/m-p/192459#M83719</guid>
      <dc:creator>Shu_ashu</dc:creator>
      <dc:date>2018-09-22T09:22:49Z</dc:date>
    </item>
  </channel>
</rss>

