Edited due to Matt Clarke's comment below: Support for Expression Language in SelectHiveQL properties was added to NiFi 1.3.0 under NIFI-3867. It is also available in HDF 3.0.x. One (less-than-ideal) workaround is to set the property to something invalid but identifiable (like "@HIVE_URL@") and have a script to replace that value in the template before uploading to a particular environment. ... View more

IIRC, Groovy 3 is supposed to support the Java lambda syntax, but NiFi uses Groovy 2 which does not support it. However Groovy has always had Closures, which are very similar and used for the same purpose, so despite a small difference in syntax, you should be able to use Groovy closures the same as you would use Java lambdas. If you are referring to the Java Streams API (things like foreach() that take a lambda), Groovy has iterative and aggregate functions for that too, such as each() and eachWithIndex(), spread-dot and collect(), etc. ... View more

Are you expecting a result set from the SELECT statement? If so then you might be better off with building a SQL query with the CLOB value inline (probably quoted and/or padded with rpad I imagine) and using ExecuteSQL vs PutSQL. The former is for queries that return result sets, the latter is for statements that don't (like INSERT). ... View more