Fun with HBasee2e2e4a7-2e3f-40a5-954b-3b7526b7ef558cf89477-3351-488d-bd8e-b4a18dbcf77a0 MB08cf89477-3351-488d-bd8e-b4a18dbcf77ab6b2d5b6-52b3-411f-8867-452f82c9deacPROCESSOR0 sec1failuresuccess05b05990c-d519-46e8-8ce0-7330d18de2478cf89477-3351-488d-bd8e-b4a18dbcf77a0 MB08cf89477-3351-488d-bd8e-b4a18dbcf77ab3f5a656-1376-4ed1-a219-d57662ff9bb2PROCESSOR0 sec1split08e1c1a01-f076-42e3-bdfa-cbfda1d99f5b8cf89477-3351-488d-bd8e-b4a18dbcf77a0 MB08cf89477-3351-488d-bd8e-b4a18dbcf77a536c8a50-0470-4cbc-bee6-91caf927e404PROCESSOR0 sec1matched0a1d0e40e-ede1-4511-9717-e361ae95c44b8cf89477-3351-488d-bd8e-b4a18dbcf77a0 MB08cf89477-3351-488d-bd8e-b4a18dbcf77ab0295f29-69e4-491e-9e2f-2cac1346c1dfPROCESSOR0 sec1matched05c4d1843-e7e2-4646-a642-38661210b8bd8cf89477-3351-488d-bd8e-b4a18dbcf77a0 MB01056.49712906174951223.99186429966471056.49712906174951273.99186429966478cf89477-3351-488d-bd8e-b4a18dbcf77ab6b2d5b6-52b3-411f-8867-452f82c9deacPROCESSOR0 sec1failure0744f9145-4ec7-4d7b-b70d-84219147a2898cf89477-3351-488d-bd8e-b4a18dbcf77a0 MB08cf89477-3351-488d-bd8e-b4a18dbcf77a26e16412-bcac-4b8b-a33a-94731c7b3510PROCESSOR0 sec1Response0e92546c1-9bc0-4449-bcbd-33b8f7cf483e8cf89477-3351-488d-bd8e-b4a18dbcf77a0 MB08cf89477-3351-488d-bd8e-b4a18dbcf77ad3fa8bd7-d978-47ac-92e5-e25a0358ec31PROCESSOR0 sec1matched0972c9849-da84-4e92-a721-58f1b1c4ee2c8cf89477-3351-488d-bd8e-b4a18dbcf77a0 MB08cf89477-3351-488d-bd8e-b4a18dbcf77acf1e53ce-5c35-4a62-ae85-5391bd6fbc13PROCESSOR0 sec1success045d0461f-76cb-4123-afc5-0c327a0580518cf89477-3351-488d-bd8e-b4a18dbcf77a0 MB01684.8846000254944855.68604079433611684.8846000254944905.68604079433618cf89477-3351-488d-bd8e-b4a18dbcf77a536c8a50-0470-4cbc-bee6-91caf927e404PROCESSOR0 sec1failure051d6230c-eb82-42cc-9933-b0ce06389a70Hadoop Configuration FilesComma-separated list of Hadoop Configuration files, such as hbase-site.xml and core-site.xml for kerberos, including full paths to the files.Hadoop Configuration FilesfalseHadoop Configuration FilesfalsefalsefalseKerberos PrincipalKerberos principal to authenticate as. Requires nifi.kerberos.krb5.file to be set in your nifi.propertiesKerberos PrincipalfalseKerberos PrincipalfalsefalsefalseKerberos KeytabKerberos keytab associated with the principal. Requires nifi.kerberos.krb5.file to be set in your nifi.propertiesKerberos KeytabfalseKerberos KeytabfalsefalsefalseZooKeeper QuorumComma-separated list of ZooKeeper hosts for HBase. Required if Hadoop Configuration Files are not provided.ZooKeeper QuorumfalseZooKeeper QuorumfalsefalsefalseZooKeeper Client PortThe port on which ZooKeeper is accepting client connections. Required if Hadoop Configuration Files are not provided.ZooKeeper Client PortfalseZooKeeper Client PortfalsefalsefalseZooKeeper ZNode ParentThe ZooKeeper ZNode Parent value for HBase (example: /hbase). Required if Hadoop Configuration Files are not provided.ZooKeeper ZNode ParentfalseZooKeeper ZNode ParentfalsefalsefalseHBase Client Retries1The number of times the HBase client will retry connecting. Required if Hadoop Configuration Files are not provided.HBase Client RetriesfalseHBase Client RetriesfalsefalsefalseHBase_1_1_2_ClientServiceHadoop Configuration Files/etc/hadoop/conf/core-site.xml,/etc/hbase/conf/hbase-site.xmlKerberos PrincipalKerberos KeytabZooKeeper QuorumZooKeeper Client PortZooKeeper ZNode ParentHBase Client Retries10HBase Client ServiceHBase_1_1_2_ClientService51d6230c-eb82-42cc-9933-b0ce06389a70Specifies the Controller Service to use for accessing HBase.HBase Client Servicefalseorg.apache.nifi.hbase.HBaseClientServiceHBase Client ServicetruefalsefalseTable NameThe name of the HBase Table to put data intoTable NamefalseTable NametruefalsetrueRow IdentifierSpecifies the Row ID to use when inserting data into HBaseRow IdentifierfalseRow IdentifierfalsefalsetrueColumn FamilyThe Column Family to use when inserting data into HBaseColumn FamilyfalseColumn FamilytruefalsetrueColumn QualifierThe Column Qualifier to use when inserting data into HBaseColumn QualifierfalseColumn QualifiertruefalsetrueBatch Size25The maximum number of FlowFiles to process in a single execution. The FlowFiles will be grouped by table, and a single Put per table will be performed.Batch SizefalseBatch Sizetruefalsefalse8cf89477-3351-488d-bd8e-b4a18dbcf77a536c8a50-0470-4cbc-bee6-91caf927e404PutHBaseCellHBase Client Service51d6230c-eb82-42cc-9933-b0ce06389a70Table NameUsersRow Identifier${ssn}Column FamilycfColumn Qualifieruser_fullBatch Size25ProcessorRUNNINGorg.apache.nifi.hbase.PutHBaseCell0HBase Client ServiceHBase_1_1_2_ClientService51d6230c-eb82-42cc-9933-b0ce06389a70Specifies the Controller Service to use for accessing HBase.HBase Client Servicefalseorg.apache.nifi.hbase.HBaseClientServiceHBase Client ServicetruefalsefalseTable NameThe name of the HBase Table to put data intoTable NamefalseTable NametruefalsetrueRow IdentifierSpecifies the Row ID to use when inserting data into HBaseRow IdentifierfalseRow IdentifierfalsefalsetrueRow Identifier Field NameSpecifies the name of a JSON element whose value should be used as the row id for the given JSON document.Row Identifier Field NamefalseRow Identifier Field NamefalsefalsetrueColumn FamilyThe Column Family to use when inserting data into HBaseColumn FamilyfalseColumn FamilytruefalsetrueBatch Size25The maximum number of FlowFiles to process in a single execution. The FlowFiles will be grouped by table, and a single Put per table will be performed.Batch SizefalseBatch SizetruefalsefalseComplex Field StrategyRoute entire FlowFile to failure if any elements contain complex values.FailFailProvide a warning and do not include field in row sent to HBase.WarnWarnSilently ignore and do not include in row sent to HBase.IgnoreIgnoreUse the string representation of the complex field as the value of the given column.TextTextTextIndicates how to handle complex fields, i.e. fields that do not have a single text value.Complex Field StrategyfalseComplex Field Strategytruefalsefalse8cf89477-3351-488d-bd8e-b4a18dbcf77ab6b2d5b6-52b3-411f-8867-452f82c9deacPutHBaseJSONHBase Client Service51d6230c-eb82-42cc-9933-b0ce06389a70Table NameUsersRow IdentifierRow Identifier Field NamessnColumn FamilycfBatch Size25Complex Field StrategyTextProcessorRUNNINGorg.apache.nifi.hbase.PutHBaseJSON0HBase Client ServiceHBase_1_1_2_ClientService51d6230c-eb82-42cc-9933-b0ce06389a70Specifies the Controller Service to use for accessing HBase.HBase Client Servicefalseorg.apache.nifi.hbase.HBaseClientServiceHBase Client ServicetruefalsefalseDistributed Cache ServiceDistributedMapCacheClientServiceba9075f5-f400-41d6-b38a-c08aa62ea7ebSpecifies the Controller Service that should be used to maintain state about what has been pulled from HBase so that if a new node begins pulling data, it won't duplicate all of the work that has been done.Distributed Cache Servicefalseorg.apache.nifi.distributed.cache.client.DistributedMapCacheClientDistributed Cache ServicefalsefalsefalseTable NameThe name of the HBase Table to put data intoTable NamefalseTable NametruefalsefalseColumnsA comma-separated list of "<colFamily>:<colQualifier>" pairs to return when scanning. To return all columns for a given family, leave off the qualifier such as "<colFamily1>,<colFamily2>".ColumnsfalseColumnsfalsefalsefalseFilter ExpressionAn HBase filter expression that will be applied to the scan. This property can not be used when also using the Columns property.Filter ExpressionfalseFilter ExpressionfalsefalsefalseInitial Time RangeNoneNoneCurrent TimeCurrent TimeNoneThe time range to use on the first scan of a table. None will pull the entire table on the first scan, Current Time will pull entries from that point forward.Initial Time RangefalseInitial Time RangetruefalsefalseCharacter SetUTF-8Specifies which character set is used to encode the data in HBaseCharacter SetfalseCharacter Settruefalsefalse8cf89477-3351-488d-bd8e-b4a18dbcf77a76e30a4e-7b40-4840-a89a-4b88d5b7b917GetHBaseHBase Client Service51d6230c-eb82-42cc-9933-b0ce06389a70Distributed Cache Serviceba9075f5-f400-41d6-b38a-c08aa62ea7ebTable NameUsersColumnsFilter ExpressionInitial Time RangeCurrent TimeCharacter SetUTF-8ProcessorRUNNINGorg.apache.nifi.hbase.GetHBaseENABLEDorg.apache.nifi.hbase.HBase_1_1_2_ClientServiceba9075f5-f400-41d6-b38a-c08aa62ea7ebServer HostnameThe name of the server that is running the DistributedMapCacheServer serviceServer HostnamefalseServer HostnametruefalsefalseServer Port4557The port on the remote server that is to be used when communicating with the DistributedMapCacheServer serviceServer PortfalseServer PorttruefalsefalseSSL Context ServiceIf specified, indicates the SSL Context Service that is used to communicate with the remote server. If not specified, communications will not be encryptedSSL Context Servicefalseorg.apache.nifi.ssl.SSLContextServiceSSL Context ServicefalsefalsefalseCommunications Timeout30 secsSpecifies how long to wait when communicating with the remote server before determining that there is a communications failure if data cannot be sent or receivedCommunications TimeoutfalseCommunications TimeouttruefalsefalseDistributedMapCacheClientServiceServer HostnamelocalhostServer Port4557SSL Context ServiceCommunications Timeout30 secs0HBase Client ServiceHBase_1_1_2_ClientService51d6230c-eb82-42cc-9933-b0ce06389a70Specifies the Controller Service to use for accessing HBase.HBase Client Servicefalseorg.apache.nifi.hbase.HBaseClientServiceHBase Client ServicetruefalsefalseDistributed Cache ServiceDistributedMapCacheClientServiceba9075f5-f400-41d6-b38a-c08aa62ea7ebSpecifies the Controller Service that should be used to maintain state about what has been pulled from HBase so that if a new node begins pulling data, it won't duplicate all of the work that has been done.Distributed Cache Servicefalseorg.apache.nifi.distributed.cache.client.DistributedMapCacheClientDistributed Cache ServicefalsefalsefalseTable NameThe name of the HBase Table to put data intoTable NamefalseTable NametruefalsefalseColumnsA comma-separated list of "<colFamily>:<colQualifier>" pairs to return when scanning. To return all columns for a given family, leave off the qualifier such as "<colFamily1>,<colFamily2>".ColumnsfalseColumnsfalsefalsefalseFilter ExpressionAn HBase filter expression that will be applied to the scan. This property can not be used when also using the Columns property.Filter ExpressionfalseFilter ExpressionfalsefalsefalseInitial Time RangeNoneNoneCurrent TimeCurrent TimeNoneThe time range to use on the first scan of a table. None will pull the entire table on the first scan, Current Time will pull entries from that point forward.Initial Time RangefalseInitial Time RangetruefalsefalseCharacter SetUTF-8Specifies which character set is used to encode the data in HBaseCharacter SetfalseCharacter Settruefalsefalse8cf89477-3351-488d-bd8e-b4a18dbcf77a76e30a4e-7b40-4840-a89a-4b88d5b7b917GetHBaseHBase Client Service51d6230c-eb82-42cc-9933-b0ce06389a70Distributed Cache Serviceba9075f5-f400-41d6-b38a-c08aa62ea7ebTable NameUsersColumnsFilter ExpressionInitial Time RangeCurrent TimeCharacter SetUTF-8ProcessorRUNNINGorg.apache.nifi.hbase.GetHBaseENABLEDorg.apache.nifi.distributed.cache.client.DistributedMapCacheClientServiceb3f5a656-1376-4ed1-a219-d57662ff9bb28cf89477-3351-488d-bd8e-b4a18dbcf77a647.2899591246951650.6413045876383WARN1TIMER_DRIVEN1EVENT_DRIVEN0CRON_DRIVEN1TIMER_DRIVEN0 secCRON_DRIVEN* * * * * ?Destinationflowfile-contentflowfile-contentflowfile-attributeflowfile-attributeflowfile-contentIndicates whether the results of the JsonPath evaluation are written to the FlowFile content or a FlowFile attribute; if using attribute, must specify the Attribute Name property. If set to flowfile-content, only one JsonPath may be specified, and the property name is ignored.DestinationfalseDestinationtruefalsefalseReturn Typeauto-detectauto-detectjsonjsonscalarscalarauto-detectIndicates the desired return type of the JSON Path expressions. Selecting 'auto-detect' will set the return type to 'json' for a Destination of 'flowfile-content', and 'scalar' for a Destination of 'flowfile-attribute'.Return TypefalseReturn TypetruefalsefalsePath Not Found BehaviorwarnwarnignoreignoreignoreIndicates how to handle missing JSON path expressions when destination is set to 'flowfile-attribute'. Selecting 'warn' will generate a warning when a JSON path expression is not found.Path Not Found BehaviorfalsePath Not Found BehaviortruefalsefalseNull Value Representationthe string 'null'the string 'null'empty stringempty stringempty stringIndicates the desired representation of JSON Path expressions resulting in a null value.Null Value RepresentationfalseNull Value RepresentationtruefalsefalseemailemailtrueemailfalsefalsefalsefirstNamefirstNametruefirstNamefalsefalsefalselastNamelastNametruelastNamefalsefalsefalsessnssntruessnfalsefalsefalsefalse30 secDestinationflowfile-attributeReturn Typeauto-detectPath Not Found BehaviorignoreNull Value Representationempty stringemail$.emailfirstName$.name.firstlastName$.name.lastssn$.id.value00 secTIMER_DRIVEN1 secEvaluateJsonPathtrueFlowFiles are routed to this relationship when the JsonPath cannot be evaluated against the content of the FlowFile; for instance, if the FlowFile is not valid JSONfailurefalseFlowFiles are routed to this relationship when the JsonPath is successfully evaluated and the FlowFile is modified as a resultmatchedtrueFlowFiles are routed to this relationship when the JsonPath does not match the content of the FlowFile and the Destination is set to flowfile-contentunmatchedRUNNINGtruetrueorg.apache.nifi.processors.standard.EvaluateJsonPathcf1e53ce-5c35-4a62-ae85-5391bd6fbc138cf89477-3351-488d-bd8e-b4a18dbcf77a1967.4143663780533548.6844856727165WARN1TIMER_DRIVEN1EVENT_DRIVEN0CRON_DRIVEN1TIMER_DRIVEN0 secCRON_DRIVEN* * * * * ?Log LeveltracetracedebugdebuginfoinfowarnwarnerrorerrorinfoThe Log Level to use when logging the AttributesLog LevelfalseLog LeveltruefalsefalseLog PayloadtruetruefalsefalsefalseIf true, the FlowFile's payload will be logged, in addition to its attributes; otherwise, just the Attributes will be logged.Log PayloadfalseLog PayloadtruefalsefalseAttributes to LogA comma-separated list of Attributes to Log. If not specified, all attributes will be logged.Attributes to LogfalseAttributes to LogfalsefalsefalseAttributes to IgnoreA comma-separated list of Attributes to ignore. If not specified, no attributes will be ignored.Attributes to IgnorefalseAttributes to IgnorefalsefalsefalseLog prefixLog prefix appended to the log lines. It helps to distinguish the output of multiple LogAttribute processors.Log prefixfalseLog prefixfalsefalsetruefalse30 secLog LevelLog PayloadAttributes to LogAttributes to IgnoreLog prefix00 secTIMER_DRIVEN1 secLogAttributetrueAll FlowFiles are routed to this relationshipsuccessRUNNINGtruetrueorg.apache.nifi.processors.standard.LogAttribute536c8a50-0470-4cbc-bee6-91caf927e4048cf89477-3351-488d-bd8e-b4a18dbcf77a1275.8846000254944830.6860407943361WARN1TIMER_DRIVEN1EVENT_DRIVEN0CRON_DRIVEN1TIMER_DRIVEN0 secCRON_DRIVEN* * * * * ?HBase Client ServiceHBase_1_1_2_ClientService51d6230c-eb82-42cc-9933-b0ce06389a70Specifies the Controller Service to use for accessing HBase.HBase Client Servicefalseorg.apache.nifi.hbase.HBaseClientServiceHBase Client ServicetruefalsefalseTable NameThe name of the HBase Table to put data intoTable NamefalseTable NametruefalsetrueRow IdentifierSpecifies the Row ID to use when inserting data into HBaseRow IdentifierfalseRow IdentifierfalsefalsetrueColumn FamilyThe Column Family to use when inserting data into HBaseColumn FamilyfalseColumn FamilytruefalsetrueColumn QualifierThe Column Qualifier to use when inserting data into HBaseColumn QualifierfalseColumn QualifiertruefalsetrueBatch Size25The maximum number of FlowFiles to process in a single execution. The FlowFiles will be grouped by table, and a single Put per table will be performed.Batch SizefalseBatch Sizetruefalsefalsefalse30 secHBase Client Service51d6230c-eb82-42cc-9933-b0ce06389a70Table NameUsersRow Identifier${ssn}Column FamilycfColumn Qualifieruser_fullBatch Size2500 secTIMER_DRIVEN1 secPutHBaseCellfalseA FlowFile is routed to this relationship if it cannot be sent to HBasefailuretrueA FlowFile is routed to this relationship after it has been successfully stored in HBasesuccessRUNNINGtruetrueorg.apache.nifi.hbase.PutHBaseCellb0295f29-69e4-491e-9e2f-2cac1346c1df8cf89477-3351-488d-bd8e-b4a18dbcf77a639.38753356861071004.8003580354857WARN1TIMER_DRIVEN1EVENT_DRIVEN0CRON_DRIVEN1TIMER_DRIVEN0 secCRON_DRIVEN* * * * * ?Attributes ListComma separated list of attributes to be included in the resulting JSON. If this value is left empty then all existing Attributes will be included. This list of attributes is case sensitive. If an attribute specified in the list is not found it will be be emitted to the resulting JSON with an empty string or NULL value.Attributes ListfalseAttributes ListfalsefalsefalseDestinationflowfile-attributeflowfile-attributeflowfile-contentflowfile-contentflowfile-attributeControl if JSON value is written as a new flowfile attribute 'JSONAttributes' or written in the flowfile content. Writing to flowfile content will overwrite any existing flowfile content.DestinationfalseDestinationtruefalsefalseInclude Core AttributestruetruefalsefalsetrueDetermines if the FlowFile org.apache.nifi.flowfile.attributes.CoreAttributes which are contained in every FlowFile should be included in the final JSON value generated.Include Core AttributesfalseInclude Core AttributestruefalsefalseNull ValuetruetruefalsefalsefalseIf true a non existing or empty attribute will be NULL in the resulting JSON. If false an empty string will be placed in the JSONNull ValuefalseNull Valuetruefalsefalsefalse30 secAttributes Listssn, firstName, lastName, emailDestinationflowfile-contentInclude Core AttributestrueNull Valuefalse00 secTIMER_DRIVEN1 secAttributesToJSONfalseFailed to convert attributes to JSONfailurefalseSuccessfully converted attributes to JSONsuccessRUNNINGtruetrueorg.apache.nifi.processors.standard.AttributesToJSON76e30a4e-7b40-4840-a89a-4b88d5b7b9178cf89477-3351-488d-bd8e-b4a18dbcf77a1961.9460725290783284.1651534753413WARN1TIMER_DRIVEN1EVENT_DRIVEN0CRON_DRIVEN1TIMER_DRIVEN0 secCRON_DRIVEN* * * * * ?HBase Client ServiceHBase_1_1_2_ClientService51d6230c-eb82-42cc-9933-b0ce06389a70Specifies the Controller Service to use for accessing HBase.HBase Client Servicefalseorg.apache.nifi.hbase.HBaseClientServiceHBase Client ServicetruefalsefalseDistributed Cache ServiceDistributedMapCacheClientServiceba9075f5-f400-41d6-b38a-c08aa62ea7ebSpecifies the Controller Service that should be used to maintain state about what has been pulled from HBase so that if a new node begins pulling data, it won't duplicate all of the work that has been done.Distributed Cache Servicefalseorg.apache.nifi.distributed.cache.client.DistributedMapCacheClientDistributed Cache ServicefalsefalsefalseTable NameThe name of the HBase Table to put data intoTable NamefalseTable NametruefalsefalseColumnsA comma-separated list of "<colFamily>:<colQualifier>" pairs to return when scanning. To return all columns for a given family, leave off the qualifier such as "<colFamily1>,<colFamily2>".ColumnsfalseColumnsfalsefalsefalseFilter ExpressionAn HBase filter expression that will be applied to the scan. This property can not be used when also using the Columns property.Filter ExpressionfalseFilter ExpressionfalsefalsefalseInitial Time RangeNoneNoneCurrent TimeCurrent TimeNoneThe time range to use on the first scan of a table. None will pull the entire table on the first scan, Current Time will pull entries from that point forward.Initial Time RangefalseInitial Time RangetruefalsefalseCharacter SetUTF-8Specifies which character set is used to encode the data in HBaseCharacter SetfalseCharacter Settruefalsefalsefalse30 secHBase Client Service51d6230c-eb82-42cc-9933-b0ce06389a70Distributed Cache Serviceba9075f5-f400-41d6-b38a-c08aa62ea7ebTable NameUsersColumnsFilter ExpressionInitial Time RangeCurrent TimeCharacter SetUTF-800 secTIMER_DRIVEN1 secGetHBasefalseAll FlowFiles are routed to this relationshipsuccessRUNNINGfalsefalseorg.apache.nifi.hbase.GetHBase104b2c73-e090-4d3e-ac89-eb28e6d466f18cf89477-3351-488d-bd8e-b4a18dbcf77a643.0279.0WARN1TIMER_DRIVEN1EVENT_DRIVEN0CRON_DRIVEN1TIMER_DRIVEN0 secCRON_DRIVEN* * * * * ?HTTP MethodGETHTTP request method (GET, POST, PUT, DELETE, HEAD, OPTIONS). Arbitrary methods are also supported. Methods other than POST and PUT will be sent without a message body.HTTP MethodfalseHTTP MethodtruefalsetrueRemote URLRemote URL which will be connected to, including scheme, host, port, path.Remote URLfalseRemote URLtruefalsetrueSSL Context ServiceThe SSL Context Service used to provide client certificate information for TLS/SSL (https) connections.SSL Context Servicefalseorg.apache.nifi.ssl.SSLContextServiceSSL Context ServicefalsefalsefalseConnection Timeout5 secsMax wait time for connection to remote service.Connection TimeoutfalseConnection TimeouttruefalsefalseRead Timeout15 secsMax wait time for response from remote service.Read TimeoutfalseRead TimeouttruefalsefalseInclude Date HeaderTrueTrueFalseFalseTrueInclude an RFC-2616 Date header in the request.Include Date HeaderfalseInclude Date HeadertruefalsefalseFollow RedirectsTrueTrueFalseFalseTrueFollow HTTP redirects issued by remote server.Follow RedirectsfalseFollow RedirectstruefalsefalseAttributes to SendRegular expression that defines which attributes to send as HTTP headers in the request. If not defined, no attributes are sent as headers. Also any dynamic properties set will be sent as headers. The dynamic property key will be the header key and the dynamic property value will be interpreted as expression language will be the header value.Attributes to SendfalseAttributes to SendfalsefalsefalseBasic Authentication UsernameThe username to be used by the client to authenticate against the Remote URL. Cannot include control characters (0-31), ':', or DEL (127).Basic Authentication UsernamefalseBasic Authentication UsernamefalsefalsefalseBasic Authentication PasswordThe password to be used by the client to authenticate against the Remote URL.Basic Authentication PasswordfalseBasic Authentication PasswordfalsetruefalseProxy HostThe fully qualified hostname or IP address of the proxy serverProxy HostfalseProxy HostfalsefalsefalseProxy PortThe port of the proxy serverProxy PortfalseProxy PortfalsefalsefalsePut Response Body In AttributeIf set, the response body received back will be put into an attribute of the original FlowFile instead of a separate FlowFile. The attribute key to put to is determined by evaluating value of this property. Put Response Body In AttributefalsePut Response Body In AttributefalsefalsetrueMax Length To Put In Attribute256If routing the response body to an attribute of the original (by setting the "Put response body in attribute" property or by receiving an error status code), the number of characters put to the attribute value will be at most this amount. This is important because attributes are held in memory and large attributes will quickly cause out of memory issues. If the output goes longer than this value, it will be truncated to fit. Consider making this smaller if able.Max Length To Put In AttributefalseMax Length To Put In AttributefalsefalsefalseDigest AuthenticationtruetruefalsefalsefalseWhether to communicate with the website using Digest Authentication. 'Basic Authentication Username' and 'Basic Authentication Password' are used for authentication.Use Digest AuthenticationfalseDigest AuthenticationfalsefalsefalseAlways Output ResponsetruetruefalsefalsefalseWill force a response FlowFile to be generated and routed to the 'Response' relationship regardless of what the server status code received is or if the processor is configured to put the server response body in the request attribute. In the later configuration a request FlowFile with the response body in the attribute and a typical response FlowFile will be emitted to their respective relationships.Always Output ResponsefalseAlways Output ResponsefalsefalsefalseTrusted HostnameBypass the normal truststore hostname verifier to allow the specified remote hostname as trusted. Enabling this property has MITM security implications, use wisely. Will still accept other connections based on the normal truststore hostname verifier. Only valid with SSL (HTTPS) connections.Trusted HostnamefalseTrusted HostnamefalsefalsefalseAdd Response Headers to RequesttruetruefalsefalsefalseEnabling this property saves all the response headers to the original request. This may be when the response headers are needed but a response is not generated due to the status code received.Add Response Headers to RequestfalseAdd Response Headers to RequestfalsefalsefalseContent-Type${mime.type}The Content-Type to specify for when content is being transmitted through a PUT or POST. In the case of an empty value after evaluating an expression language expression, Content-Type defaults to application/octet-streamContent-TypefalseContent-TypetruefalsetrueUse Chunked EncodingtruetruefalsefalsefalseWhen POST'ing or PUT'ing content set this property to true in order to not pass the 'Content-length' header and instead send 'Transfer-Encoding' with a value of 'chunked'. This will enable the data transfer mechanism which was introduced in HTTP 1.1 to pass data of unknown lengths in chunks.Use Chunked EncodingfalseUse Chunked EncodingtruefalsefalsePenalize on "No Retry"truetruefalsefalsefalseEnabling this property will penalize FlowFiles that are routed to the "No Retry" relationship.Penalize on "No Retry"falsePenalize on "No Retry"falsefalsefalsefalse30 secHTTP MethodGETRemote URLhttp://api.randomuser.me?nat=us&results=1000SSL Context ServiceConnection Timeout5 secsRead Timeout15 secsInclude Date HeaderTrueFollow RedirectsTrueAttributes to SendBasic Authentication UsernameBasic Authentication PasswordProxy HostProxy PortPut Response Body In AttributeMax Length To Put In Attribute256Digest AuthenticationfalseAlways Output ResponsefalseTrusted HostnameAdd Response Headers to RequestfalseContent-Type${mime.type}Use Chunked EncodingfalsePenalize on "No Retry"false01 minsTIMER_DRIVEN1 secFetch User DatatrueThe original FlowFile will be routed on any type of connection failure, timeout or general exception. It will have new attributes detailing the request.FailuretrueThe original FlowFile will be routed on any status code that should NOT be retried (1xx, 3xx, 4xx status codes). It will have new attributes detailing the request.No RetrytrueThe original FlowFile will be routed upon success (2xx status codes). It will have new attributes detailing the success of the request.OriginalfalseA Response FlowFile will be routed upon success (2xx status codes). If the 'Output Response Regardless' property is true then the response will be sent to this relationship regardless of the status code received.ResponsetrueThe original FlowFile will be routed on any status code that can be retried (5xx status codes). It will have new attributes detailing the request.RetrySTOPPEDfalsetrueorg.apache.nifi.processors.standard.InvokeHTTP26e16412-bcac-4b8b-a33a-94731c7b35108cf89477-3351-488d-bd8e-b4a18dbcf77a646.3367037460112474.62539406580777WARN1TIMER_DRIVEN1EVENT_DRIVEN0CRON_DRIVEN1TIMER_DRIVEN0 secCRON_DRIVEN* * * * * ?JsonPath ExpressionA JsonPath expression that indicates the array element to split into JSON/scalar fragments.JsonPath ExpressionfalseJsonPath ExpressiontruefalsefalseNull Value Representationthe string 'null'the string 'null'empty stringempty stringempty stringIndicates the desired representation of JSON Path expressions resulting in a null value.Null Value RepresentationfalseNull Value Representationtruefalsefalsefalse30 secJsonPath Expression$.results[*]Null Value Representationempty string00 secTIMER_DRIVEN1 secSplitJsontrueIf a FlowFile fails processing for any reason (for example, the FlowFile is not valid JSON or the specified path does not exist), it will be routed to this relationshipfailuretrueThe original FlowFile that was split into segments. If the FlowFile fails processing, nothing will be sent to this relationshiporiginalfalseAll segments of the original FlowFile will be routed to this relationshipsplitRUNNINGtruetrueorg.apache.nifi.processors.standard.SplitJsond3fa8bd7-d978-47ac-92e5-e25a0358ec318cf89477-3351-488d-bd8e-b4a18dbcf77a643.06201171875836.3800048828125WARN1TIMER_DRIVEN1EVENT_DRIVEN0CRON_DRIVEN1TIMER_DRIVEN0 secCRON_DRIVEN* * * * * ?Routing StrategyA copy of the FlowFile will be routed to each relationship whose corresponding expression evaluates to 'true'Route to Property nameRoute to Property nameRequires that all user-defined expressions evaluate to 'true' for the FlowFile to be considered a matchRoute to 'matched' if all matchRoute to 'match' if all matchRequires that at least one user-defined expression evaluate to 'true' for the FlowFile to be considered a matchRoute to 'matched' if any matchesRoute to 'match' if any matchesRoute to Property nameSpecifies how to determine which relationship to use when evaluating the Expression LanguageRouting StrategyfalseRouting Strategytruefalsefalsematchedmatchedtruematchedfalsefalsetruefalse30 secRouting StrategyRoute to Property namematched${ssn:isEmpty():not()}00 secTIMER_DRIVEN1 secRouteOnAttributefalsematchedtrueFlowFiles that do not match any user-define expression will be routed hereunmatchedRUNNINGtruetrueorg.apache.nifi.processors.standard.RouteOnAttributeb6b2d5b6-52b3-411f-8867-452f82c9deac8cf89477-3351-488d-bd8e-b4a18dbcf77a647.49712906174951198.9918642996647WARN1TIMER_DRIVEN1EVENT_DRIVEN0CRON_DRIVEN1TIMER_DRIVEN0 secCRON_DRIVEN* * * * * ?HBase Client ServiceHBase_1_1_2_ClientService51d6230c-eb82-42cc-9933-b0ce06389a70Specifies the Controller Service to use for accessing HBase.HBase Client Servicefalseorg.apache.nifi.hbase.HBaseClientServiceHBase Client ServicetruefalsefalseTable NameThe name of the HBase Table to put data intoTable NamefalseTable NametruefalsetrueRow IdentifierSpecifies the Row ID to use when inserting data into HBaseRow IdentifierfalseRow IdentifierfalsefalsetrueRow Identifier Field NameSpecifies the name of a JSON element whose value should be used as the row id for the given JSON document.Row Identifier Field NamefalseRow Identifier Field NamefalsefalsetrueColumn FamilyThe Column Family to use when inserting data into HBaseColumn FamilyfalseColumn FamilytruefalsetrueBatch Size25The maximum number of FlowFiles to process in a single execution. The FlowFiles will be grouped by table, and a single Put per table will be performed.Batch SizefalseBatch SizetruefalsefalseComplex Field StrategyRoute entire FlowFile to failure if any elements contain complex values.FailFailProvide a warning and do not include field in row sent to HBase.WarnWarnSilently ignore and do not include in row sent to HBase.IgnoreIgnoreUse the string representation of the complex field as the value of the given column.TextTextTextIndicates how to handle complex fields, i.e. fields that do not have a single text value.Complex Field StrategyfalseComplex Field Strategytruefalsefalsefalse30 secHBase Client Service51d6230c-eb82-42cc-9933-b0ce06389a70Table NameUsersRow IdentifierRow Identifier Field NamessnColumn FamilycfBatch Size25Complex Field StrategyText00 secTIMER_DRIVEN1 secPutHBaseJSONfalseA FlowFile is routed to this relationship if it cannot be sent to HBasefailuretrueA FlowFile is routed to this relationship after it has been successfully stored in HBasesuccessRUNNINGtruetrueorg.apache.nifi.hbase.PutHBaseJSON05/06/2016 13:31:24 UTC