<?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: NiFi Code to Description mapping in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Code-to-Description-mapping/m-p/116803#M46995</link>
    <description>&lt;P&gt;This is a pretty common pattern and something we should add more out of the box support for.  This is a lot like how the GeoEnrich processor works.  There is some reference dataset and some incoming data which needs to be enriched/altered based on pulling keys from the data and looking up their values in the dataset.&lt;/P&gt;&lt;P&gt;I'd recommend you provide a ControllerService that loads/monitors changes to your reference dataset that offers a 'get(key)' type lookup where the value returned is the value you want to place into your data.&lt;/P&gt;&lt;P&gt;Then provide a custom processor that uses that controller service against your data.  You could do both of these using the scripting support in Groovy, for example.&lt;/P&gt;&lt;P&gt;You could also just do this in a single processor as well.&lt;/P&gt;&lt;P&gt;Hope that helps&lt;/P&gt;</description>
    <pubDate>Wed, 23 Nov 2016 01:13:39 GMT</pubDate>
    <dc:creator>JoeWitt</dc:creator>
    <dc:date>2016-11-23T01:13:39Z</dc:date>
    <item>
      <title>NiFi Code to Description mapping</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Code-to-Description-mapping/m-p/116801#M46993</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Wanted to find out what's the NiFi best practice for a use case I am working on; &lt;/P&gt;&lt;P&gt;The incoming data has codes and the codes should be replaced with the corresponding code descriptions, from a manually maintained static (almost static, rarely changes) list of codes and their corresponding descriptions in a file.&lt;/P&gt;&lt;P&gt;Is ReplaceTextWithMapping the right processor to implement this.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2016 01:07:24 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Code-to-Description-mapping/m-p/116801#M46993</guid>
      <dc:creator>Raj_B</dc:creator>
      <dc:date>2016-11-23T01:07:24Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi Code to Description mapping</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Code-to-Description-mapping/m-p/116802#M46994</link>
      <description>&lt;P&gt;Depending on the format of your data, you might be better off using the ScanAttribute &lt;A target="_blank" href="https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.ScanAttribute/index.html"&gt;https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.ScanAttribute/index.html&lt;/A&gt; It will reference an external file for a match and route the flowfile accordingly. E.g. follow up with an UpdateAttribute to update/add to the metadata.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2016 01:11:21 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Code-to-Description-mapping/m-p/116802#M46994</guid>
      <dc:creator>andrewg</dc:creator>
      <dc:date>2016-11-23T01:11:21Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi Code to Description mapping</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Code-to-Description-mapping/m-p/116803#M46995</link>
      <description>&lt;P&gt;This is a pretty common pattern and something we should add more out of the box support for.  This is a lot like how the GeoEnrich processor works.  There is some reference dataset and some incoming data which needs to be enriched/altered based on pulling keys from the data and looking up their values in the dataset.&lt;/P&gt;&lt;P&gt;I'd recommend you provide a ControllerService that loads/monitors changes to your reference dataset that offers a 'get(key)' type lookup where the value returned is the value you want to place into your data.&lt;/P&gt;&lt;P&gt;Then provide a custom processor that uses that controller service against your data.  You could do both of these using the scripting support in Groovy, for example.&lt;/P&gt;&lt;P&gt;You could also just do this in a single processor as well.&lt;/P&gt;&lt;P&gt;Hope that helps&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2016 01:13:39 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Code-to-Description-mapping/m-p/116803#M46995</guid>
      <dc:creator>JoeWitt</dc:creator>
      <dc:date>2016-11-23T01:13:39Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi Code to Description mapping</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Code-to-Description-mapping/m-p/116804#M46996</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/10100/rbolla.html" nodeid="10100"&gt;@Raj B&lt;/A&gt; I laid out some of the options in a recent mailing list discussion [1]. These include both of the suggestions above, including a link to a work-in-progress implementation for the ControllerService approach.&lt;/P&gt;&lt;P&gt;1. &lt;A href="http://mail-archives.apache.org/mod_mbox/nifi-dev/201611.mbox/%3c31b8fe4f-95f6-4419-80a9-f9a728a9cb7c@me.com%3e"&gt;http://mail-archives.apache.org/mod_mbox/nifi-dev/201611.mbox/%3c31b8fe4f-95f6-4419-80a9-f9a728a9cb7c@me.com%3e&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2016 01:19:40 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Code-to-Description-mapping/m-p/116804#M46996</guid>
      <dc:creator>jfrazee</dc:creator>
      <dc:date>2016-11-23T01:19:40Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi Code to Description mapping</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Code-to-Description-mapping/m-p/116805#M46997</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/2956/jfrazee.html" nodeid="2956"&gt;@jfrazee&lt;/A&gt; &lt;A rel="user" href="https://community.cloudera.com/users/173/agrande.html" nodeid="173"&gt;@Andrew Grande&lt;/A&gt; &lt;A rel="user" href="https://community.cloudera.com/users/364/jwitt.html" nodeid="364"&gt;@jwitt&lt;/A&gt; thank you all for the ideas and information.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2016 02:14:36 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Code-to-Description-mapping/m-p/116805#M46997</guid>
      <dc:creator>Raj_B</dc:creator>
      <dc:date>2016-11-23T02:14:36Z</dc:date>
    </item>
  </channel>
</rss>

