Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 03-29-2017 08:30 PM
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.
Created 03-30-2017 01:30 PM
Yes in nifi.properties see the following properties:
# Comma-separated list of fields. Fields that are not indexed will not be searchable. Valid fields are:
# EventType, FlowFileUUID, Filename, TransitURI, ProcessorID, AlternateIdentifierURI, Relationship, Details nifi.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, ProcessorID, Relationship
# FlowFile Attributes that should be indexed and made searchable. Some examples to consider are filename, uuid, mime.type nifi.provenance.repository.indexed.attributes=
Created 03-30-2017 01:30 PM
Yes in nifi.properties see the following properties:
# Comma-separated list of fields. Fields that are not indexed will not be searchable. Valid fields are:
# EventType, FlowFileUUID, Filename, TransitURI, ProcessorID, AlternateIdentifierURI, Relationship, Details nifi.provenance.repository.indexed.fields=EventType, FlowFileUUID, Filename, ProcessorID, Relationship
# FlowFile Attributes that should be indexed and made searchable. Some examples to consider are filename, uuid, mime.type nifi.provenance.repository.indexed.attributes=
Created 02-20-2019 07:50 PM
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?