Github user patricker commented on the issue:
https://github.com/apache/nifi/pull/1281
@mattyb149 I've completed the changes. I added support for
GenerateTableFetch, though Hive being hive it's not all that fast...
There is one quirk, and I feel it should be documented but I'm not sure
where. When using QueryDatabaseAdapter with Hive you need to qualify your max
value column with the table name. This is because Hive always qualifies the
column names in the ResultSet. Also, as a result of this, you'll need to
Normalize the column names.
With GenerateTableFetch, since it pulls back the max value through a query
and aliases the column name, I don't think the above issue is a problem.
ExecuteSQL should work without any special changes, just remember to select
a Database Adapter when testing HIVE, this didn't used to be an available
option.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
