RecordReaderFactory
Implementations: JsonPathReader
Syslog5424Reader
CSVReader
JsonTreeReader
GrokReader
ExcelReader
ParquetReader
ReaderLookup
CEFReader
WindowsEventLogReader
ProtobufReader
SyslogReader
AvroReader
XMLReader
ScriptedReader
YamlTreeReader
Specifies the Controller Service to use for parsing incoming data and determining the data's schema | Record Writer | record-writer | | Controller Service API: RecordSetWriterFactory Implementations: ScriptedRecordSetWriter ParquetRecordSetWriter RecordSetWriterLookup CSVRecordSetWriter FreeFormTextRecordSetWriter JsonRecordSetWriter AvroRecordSetWriter XMLRecordSetWriter | Specifies the Controller Service to use for writing results to a FlowFile |
Include Zero Record FlowFiles | include-zero-record-flowfiles | true | | When running the SQL statement against an incoming FlowFile, if the result has no data, this property specifies whether or not a FlowFile will be sent to the corresponding relationship |
Cache Schema | cache-schema | true | | This property is no longer used. It remains solely for backward compatibility in order to avoid making existing Processors invalid upon upgrade. This property will be removed in future versions. Now, instead of forcing the user to understand the semantics of schema caching, the Processor caches up to 25 schemas and automatically rolls off the old schemas. This provides the same performance when caching was enabled previously and in some cases very significant performance improvements if caching was previously disabled. |
Default Decimal Precision | dbf-default-precision | 10 | | When a DECIMAL/NUMBER value is written as a 'decimal' Avro logical type, a specific 'precision' denoting number of available digits is required. Generally, precision is defined by column data type definition or database engines default. However undefined precision (0) can be returned from some database engines. 'Default Decimal Precision' is used when writing those undefined precision numbers. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
Default Decimal Scale | dbf-default-scale | 0 | | When a DECIMAL/NUMBER value is written as a 'decimal' Avro logical type, a specific 'scale' denoting number of available decimal digits is required. Generally, scale is defined by column data type definition or database engines default. However when undefined precision (0) is returned, scale can also be uncertain with some database engines. 'Default Decimal Scale' is used when writing those undefined numbers. If a value has more decimals than specified scale, then the value will be rounded-up, e.g. 1.53 becomes 2 with scale 0, and 1.5 with scale 1. Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
Dynamic Properties:
Supports Sensitive Dynamic Properties: No
Dynamic Properties allow the user to specify both the name and value of a property.
Name | Value | Description |
---|
The name of the relationship to route data to | A SQL SELECT statement that is used to determine what data should be routed to this relationship. | Each user-defined property specifies a SQL SELECT statement to run over the data, with the data that is selected being routed to the relationship whose name is the property name Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
Relationships:
Name | Description |
---|
failure | If a FlowFile fails processing for any reason (for example, the SQL statement contains columns not present in input data), the original FlowFile it will be routed to this relationship |
original | The original FlowFile is routed to this relationship |
Dynamic Relationships:
A Dynamic Relationship may be created based on how the user configures the Processor.
Name | Description |
---|
<Property Name> | Each user-defined property defines a new Relationship for this Processor. |
Reads Attributes:
None specified.Writes Attributes:
Name | Description |
---|
mime.type | Sets the mime.type attribute to the MIME Type specified by the Record Writer |
record.count | The number of records selected by the query |
QueryRecord.Route | The relation to which the FlowFile was routed |
State management:
This component does not store state.Restricted:
This component is not restricted.Input requirement:
This component requires an incoming relationship.System Resource Considerations:
None specified.