Support Questions
Find answers, ask questions, and share your expertise

Is there any way in NiFi to add custom fields as part of the "search events" option in Data Provenance feature.

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.

1 ACCEPTED SOLUTION

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=

View solution in original post

2 REPLIES 2

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=

Contributor

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?

Take a Tour of the Community
Don't have an account?
Your experience may be limited. Sign in to explore more.