This is a known issue when Phoenix is installed: https://issues.apache.org/jira/browse/NIFI-1712 https://github.com/apache/nifi/pull/1156 Only work around currently is to copy phoenix-client.jar to the appropriate nifi/work/nar directory to get it on the HBase processor's classpath. ... View more

Some of these properties are a little bit mis-leading and were renamed in 1.0 to make it clearer: https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#kerberos_properties I think if you are calling an external script you would need to handle renewing the kerberos tickets yourself. You could just setup a GenerateFlowFile on a timer schedule that went to an ExecuteStreamCommand and just did a kinit every couple of hours. ... View more

LogAttribute relies on the logback configuration that everything uses in NiFi uses for logging (logback.xml in conf). Right now it goes into nifi-app.log which is the default appender, but you could probably create a new file appender for something like "nifi-logatttribute.log" and then modify this line: <logger name="org.apache.nifi.processors.standard.LogAttribute" level="INFO"/> To be something like: <logger name="org.apache.nifi.processors.standard.LogAttribute" level="INFO"> <appender-ref ref="LOGATTRIBUTE_FILE" /> </logger> Assuming you defined a file appender named LOGATTRIBUTE_FILE. ... View more

I believe you can do what you described... You would select "User-Defined" as the partition strategy, which means it will send to the partition provided in the "Partition" property. Since "Partition" supports expression language, this could be a reference to an attribute of an incoming flow file such as ${partition}. If I am understanding your scenario correctly, lets say you flow files with a "type" attribute that can be either "A" or "B", and you want all "A" messages to go to partition 1 and all B messages to partition 2. You could use a RouteOnAttribute processor to route A message to one relationship, and B messages to the other, and then for each of them have an UpdateAttribute processor that adds a new attribute like partition = 1 or partition = 2, so that when it gets to PutKafka you can reference ${partition}. ... View more