ConvertJSONToDocuments
Many systems can output data in JSON format. The ConvertJSONToDocuments processor detects any FlowFile that represents a JSON file and attempts to parse the JSON into IDOL documents. The processor produces a new FlowFile for each IDOL document. If an input FlowFile does not represent a file in JSON format, the processor transfers the FlowFile to the "unprocessed" relationship.
Properties
Name | Default Value | Description |
---|---|---|
IDOL License Service |
An IdolLicenseServiceImpl that provides a way to communicate with an IDOL License Server. |
|
Document Registry Service | A DocumentRegistryServiceImpl controller service that manages and updates a document registry database. This ensures that documents are indexed in the correct order. | |
JSON Parsing Config | A collection of configuration parameters that configure JSON Parsing. The parameters that you can use are the same as those in the [JSONParsing] section of the CFS configuration file. (In the NiFi processor configuration, do not include the [JSONParsing] section header). For more information about these parameters, refer to the Connector Framework Server Reference. |
|
Commit Batch Size | 100 | The processor outputs documents in batches to limit memory use and allow subsequent tasks to begin processing the documents sooner. This property specifies the maximum batch size. |
Relationships
Name | Description |
---|---|
extracted | New FlowFiles (individual IDOL documents that were extracted). |
failure | Original FlowFiles that represent a JSON file, but resulted in parsing errors. |
processed | Original FlowFiles that represent a JSON file, and were parsed successfully. Original FlowFiles are routed to this relationship when they contain valid IDOL documents. |
unprocessed | Original FlowFiles that do not represent a JSON file. |