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]

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

HIVE insert/update/delete

avatar
Super Collaborator

Hi All,

I tried HIVE insert/update/delete operations, I see that it launches a tez job and bit slow. I have a couple of questions -

1. when we use hive streaming processors (in nifi, streamsets) does it insert record by record? I believe no. just to confirm.

2. it seems bit risky to design an acid hive table, is there an approach where it can be used (such as IOT ) safely without having locking/concurrency issues etc.

Thanks,

Avijeet

1 ACCEPTED SOLUTION

avatar
Super Collaborator

In Nifi, you can use the PutHiveStreaming processor, and it is designed to commit transactions in batch, which is configurable.

https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.2.0/org.apache.nif...

I think risky is not the correct term for using an ACID table, but careful may be better; that is, with careful design and configuration, you can avoid locking issues. Be sure to review the Hive documentation on this:

https://cwiki.apache.org/confluence/display/Hive/Hive+Transactions

View solution in original post

1 REPLY 1

avatar
Super Collaborator

In Nifi, you can use the PutHiveStreaming processor, and it is designed to commit transactions in batch, which is configurable.

https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.2.0/org.apache.nif...

I think risky is not the correct term for using an ACID table, but careful may be better; that is, with careful design and configuration, you can avoid locking issues. Be sure to review the Hive documentation on this:

https://cwiki.apache.org/confluence/display/Hive/Hive+Transactions