<?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 Is there any way in NiFi to add custom fields as part of the &amp;quot;search events&amp;quot; option in Data Provenance feature. in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-there-any-way-in-NiFi-to-add-custom-fields-as-part-of-the/m-p/179918#M58516</link>
    <description>&lt;P&gt;The idea is to add search criteria based on custom field (part of the event) based on some unique identifier ( e.g. Order Number) . This will help in identifying the unique transaction details. Please suggest if there is any other alternatives to achieve this.&lt;/P&gt;</description>
    <pubDate>Thu, 30 Mar 2017 03:30:36 GMT</pubDate>
    <dc:creator>mpandit</dc:creator>
    <dc:date>2017-03-30T03:30:36Z</dc:date>
    <item>
      <title>Is there any way in NiFi to add custom fields as part of the "search events" option in Data Provenance feature.</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-there-any-way-in-NiFi-to-add-custom-fields-as-part-of-the/m-p/179918#M58516</link>
      <description>&lt;P&gt;The idea is to add search criteria based on custom field (part of the event) based on some unique identifier ( e.g. Order Number) . This will help in identifying the unique transaction details. Please suggest if there is any other alternatives to achieve this.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 03:30:36 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-there-any-way-in-NiFi-to-add-custom-fields-as-part-of-the/m-p/179918#M58516</guid>
      <dc:creator>mpandit</dc:creator>
      <dc:date>2017-03-30T03:30:36Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way in NiFi to add custom fields as part of the "search events" option in Data Provenance feature.</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-there-any-way-in-NiFi-to-add-custom-fields-as-part-of-the/m-p/179919#M58517</link>
      <description>&lt;P&gt;Yes in nifi.properties see the following properties:&lt;/P&gt;&lt;P&gt;# Comma-separated list of fields. Fields that are not indexed will not be searchable. Valid fields are: &lt;/P&gt;&lt;P&gt;# EventType, FlowFileUUID, Filename, TransitURI, ProcessorID, AlternateIdentifierURI, Relationship, Details
nifi.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, ProcessorID, Relationship &lt;/P&gt;&lt;P&gt;# FlowFile Attributes that should be indexed and made searchable.  Some examples to consider are filename, uuid, mime.type
nifi.provenance.repository.indexed.attributes=&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 20:30:42 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-there-any-way-in-NiFi-to-add-custom-fields-as-part-of-the/m-p/179919#M58517</guid>
      <dc:creator>bbende</dc:creator>
      <dc:date>2017-03-30T20:30:42Z</dc:date>
    </item>
    <item>
      <title>Re: Is there any way in NiFi to add custom fields as part of the "search events" option in Data Provenance feature.</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-there-any-way-in-NiFi-to-add-custom-fields-as-part-of-the/m-p/179920#M58518</link>
      <description>&lt;P&gt;I believe the ask was can we add "Custom Fields" eg; new fields other that the defined "valid" fields. How can I add pat or time stamp etc?&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 03:50:26 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Is-there-any-way-in-NiFi-to-add-custom-fields-as-part-of-the/m-p/179920#M58518</guid>
      <dc:creator>wjsandman</dc:creator>
      <dc:date>2019-02-21T03:50:26Z</dc:date>
    </item>
  </channel>
</rss>

