The documents at the link above are for Apache NiFi 1.1.0, but HDF 2.0.0 was built with NiFi 1.0.0. The ability to append was added to NiFi 1.1.0 under NIFI-1322, so will likely be available in an upcoming version of HDF. The docs at that site are always for the latest version of Apache NiFi, it is recommended that you use the docs that come with your version of HDF/NiFi, using the Help option from the top-right hamburger menu in your running instance of HDF/NiFi. ... View more

So if the customer_name value for id=CCCDD was "Matt" then you'd like the first output row to read: XXXXX, BBBBB, CCCCC, CCCDD, Matt Is that correct? If so, you could do the following: Use SplitText to split the incoming CSV into one flow file per line ExtractText to store the four column values as attributes (example template called Working_With_CSV here), let's assume the attribute for the fourth column is called "column.4" ReplaceText to set the content of the flow file to a SQL statement "select customer_name from table where id=${column.4} limit 1" ExecuteSQL to execute the statement ConvertAvroToJson to get the record into JSON (for further processing) EvaluateJsonPath to get the value of customer_name into an attribute (named "customer.name" with a JSON Path of $[0].customer_name or something like that) ReplaceText to set the row back to the original columns plus the new one, with something like "${column.1},${column.2},${column.3},${column.4}, ${customer.name}" (optional) MergeContent to join the rows back together (if you need them as one file) ... View more

Your original URL "jdbc://hive2://localhost:10000/default" has slashes between jdbc: and hive2, this should instead be jdbc:hive2://localhost:10000/default For the zookeeper version of the URL, that is a known issue (NIFI-2575), I would recommend correcting the original URL and using that (port 10000 should be opened/forwarded on the sandbox already). ... View more

There is a table for JDBC type values here, for your data types they are as follows: Type Value INTEGER 4 TIMESTAMP 93 DOUBLE 8 LONGVARCHAR -1 ... View more

Each processor is responsible for reading and writing whichever attributes it wants to for the purposes of its processing, and those attributes are available in each processor's documentation. SplitJson for example writes the following attributes to each output flow file: Name Description fragment.identifier All split FlowFiles produced from the same parent FlowFile will have the same randomly generated UUID added for this attribute fragment.index A one-up number that indicates the ordering of the split FlowFiles that were created from a single parent FlowFile fragment.count The number of split FlowFiles generated from the parent FlowFile segment.original.filename The filename of the parent FlowFile These were added to NiFi 1.0.0 (HDF 2.0) under NIFI-2632, so if you are using a version of NiFi/HDF before that, that's why you won't see these attributes populated by SplitJson. ... View more