Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]
Created 09-09-2016 01:06 PM
Hi,
I noticed that the only configurable part in PutHiveQL processor is Hive Database Connection Pooling Service Name. And this needs to be setup as a controller service. So i'm wondering where to mention the actual insert statement or query which will do the job. Does this imply that there has to be other processor preceding to it with a means to generate insert queries that are specific to where and how we want the data in Hive and is fed to this processor as flowfiles?
Created 09-09-2016 01:10 PM
Sam, the statements should be in the flowfile content/payload. Please see https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.hive.PutHiveQL/index.ht...
Also, it's not limited to INSERT statements only, any Hive DDL will be executed by this processor as well. This becomes very useful for creating new partitions in a table, etc.
Created 09-09-2016 01:10 PM
Sam, the statements should be in the flowfile content/payload. Please see https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.hive.PutHiveQL/index.ht...
Also, it's not limited to INSERT statements only, any Hive DDL will be executed by this processor as well. This becomes very useful for creating new partitions in a table, etc.
Created 09-13-2016 04:37 AM
Thanks for the clarification.