<?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 Best Practices: Processor Naming Conventions in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Best-Practices-Processor-Naming-Conventions/m-p/189544#M65205</link>
    <description>&lt;P&gt;Glad it helped.  I wanted to note that since &lt;A rel="user" href="https://community.cloudera.com/users/10930/scarroll.html" nodeid="10930"&gt;@Sebastian Carroll&lt;/A&gt; posted his great blog, component alignment functionality was added in NiFi 1.2.0, so it is much easier to line up components on the canvas.  I described it here:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hortonworks.com/content/kbentry/106723/new-ui-enhancements-in-apache-nifi-12.html"&gt;https://community.hortonworks.com/content/kbentry/106723/new-ui-enhancements-in-apache-nifi-12.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 22 Jul 2017 03:32:56 GMT</pubDate>
    <dc:creator>alim</dc:creator>
    <dc:date>2017-07-22T03:32:56Z</dc:date>
    <item>
      <title>NiFi Best Practices: Processor Naming Conventions</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Best-Practices-Processor-Naming-Conventions/m-p/189541#M65202</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;Do we have any "best practices" documentation or guidelines on how to name Processors in Configure &amp;gt; Settings &amp;gt; Name?&lt;/P&gt;&lt;P&gt;Thanks!!&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jul 2017 22:09:30 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Best-Practices-Processor-Naming-Conventions/m-p/189541#M65202</guid>
      <dc:creator>mayank_rathi</dc:creator>
      <dc:date>2017-07-19T22:09:30Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi Best Practices: Processor Naming Conventions</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Best-Practices-Processor-Naming-Conventions/m-p/189542#M65203</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/19359/mayankrathi.html" nodeid="19359"&gt;@M R&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;Are the NiFi flows used/maintained by multiple parties?  If so, it would make sense to determine a naming convention as a group so that it is done consistently across your team.  In general, I think you want to give longer, unique and descriptive names to each processor so that it can be easily and quickly understood what it does and what role it plays in the flow. This is especially useful when you are trying to locate a particular processor but there are multiple processors in your flow that are the same type.&lt;/P&gt;&lt;P&gt;A good resource for keeping flows maintainable that has a section on naming can be found here:&lt;/P&gt;&lt;P&gt;&lt;A href="http://sebastiancarroll.github.io/2017/03/15/keeping-your-dataflows-tidy.html" target="_blank"&gt;http://sebastiancarroll.github.io/2017/03/15/keeping-your-dataflows-tidy.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jul 2017 23:07:27 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Best-Practices-Processor-Naming-Conventions/m-p/189542#M65203</guid>
      <dc:creator>alim</dc:creator>
      <dc:date>2017-07-19T23:07:27Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi Best Practices: Processor Naming Conventions</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Best-Practices-Processor-Naming-Conventions/m-p/189543#M65204</link>
      <description>&lt;P&gt;Yes. Possibly maintained by different parties across several time zones. Thanks for sharing such a great link.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jul 2017 02:33:55 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Best-Practices-Processor-Naming-Conventions/m-p/189543#M65204</guid>
      <dc:creator>mayank_rathi</dc:creator>
      <dc:date>2017-07-21T02:33:55Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi Best Practices: Processor Naming Conventions</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Best-Practices-Processor-Naming-Conventions/m-p/189544#M65205</link>
      <description>&lt;P&gt;Glad it helped.  I wanted to note that since &lt;A rel="user" href="https://community.cloudera.com/users/10930/scarroll.html" nodeid="10930"&gt;@Sebastian Carroll&lt;/A&gt; posted his great blog, component alignment functionality was added in NiFi 1.2.0, so it is much easier to line up components on the canvas.  I described it here:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.hortonworks.com/content/kbentry/106723/new-ui-enhancements-in-apache-nifi-12.html"&gt;https://community.hortonworks.com/content/kbentry/106723/new-ui-enhancements-in-apache-nifi-12.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 22 Jul 2017 03:32:56 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/NiFi-Best-Practices-Processor-Naming-Conventions/m-p/189544#M65205</guid>
      <dc:creator>alim</dc:creator>
      <dc:date>2017-07-22T03:32:56Z</dc:date>
    </item>
  </channel>
</rss>

