NiFi Ingest
23.3.0
New Features
- NiFi Ingest can enrich IDOL documents by adding more information about a user. There are two new processors, named EnrichUserFromAzureAD and EnrichUserFromLDAP. These query Azure AD or an LDAP directory to obtain information about a user, and add the information to the IDOL document. The processors can read a user ID or e-mail address from either a FlowFile attribute or an IDOL document metadata field. You might use one of these processors when a connector writes a user ID to an IDOL document, and you want to add more information about the user, such as their display name.
- The Eduction processor can extract entities from tables (such as comma-separated or tab-separated data, or the output from KeyView filtering when you set "Output Table Info" to
TRUE
), using information in the table headers to provide context. For more information about the supported table formats, refer to the Eduction documentation. - The Universal Redaction template supports tables detected by OCR.
- IDOL NiFi connectors support a new advanced property named
adv:AllowedClusterNodesRegex
. By default, a connector runs on all nodes of a cluster. If you set this property the connector runs only on nodes where the hostname matches the specified regular expression.
Resolved Issues
- NiFi could terminate unexpectedly when a NiFi Ingest media processor (for example the OpticalCharacterRecognition processor) was used to process an image with a very large number of pixels.
-
The Content component NiFi processor,
ContentServiceImpl
was unable to obtain a license correctly.
Notes
- When you use the ContentFromHTML or RenderHTML processors, the embedded web browser is no longer permitted to navigate away from the source page. If necessary you can allow navigation by setting the new configuration parameter
AllowNavigations=TRUE
.
23.2.0
New Features
- The ConvertXMLToDocuments processor has a guided setup wizard.
- The performance of external ODBC datastores has been improved (connectors store their state information in an external database when you set the State Database Service property).
Resolved Issues
- Lower than expected performance was observed when using an external document registry database. This could result in slow indexing, for example with the PutIDOL processor. The performance of the document registry has been improved.
- The KeyViewFilterDocument processor could fail to process FlowFiles, reporting the error "An invalid or illegal xml character is specified".
- The RemoveDocumentPart processor did not delete temporary .MSG or .EML files if it was used in a dataflow following a KeyViewExtractFiles processor with the "Merge mails" property set to TRUE.
- Reduced memory usage for some IDOL NiFi processors.
- The OpticalCharacterRecognition processor could terminate unexpectedly.
- When using the OpticalCharacterRecognition processor, some temporary files produced by KeyView were written to the system temporary directory, rather than the location specified in the KeyView Export Service. Some temporary files were not deleted when no longer required.
Notes
- The minimum version of Apache NiFi supported by the IDOL NiFi Ingest components is now NiFi 1.15.3.
- Due to an issue with the storage of OAuth tokens in previous versions of the RMSDecrypt and RMSEncrypt processors, you might need to obtain OAuth tokens again.
Deprecated Features
The following features are deprecated and might be removed in a future release.
Category | Deprecated Feature | Deprecated Since |
---|---|---|
Clipping | In the ContentFromHTML and RenderHTML processors, the SMARTPRINT clipping mode has been deprecated. |
23.3.0 |