Hi, I am connecting to the Hive Server using TCD eclipse plugin and running HIVE QL commands. One question that i had was how do i run multiple queries in one session? What im trying to do is run commands like:add jar jarname;create temporary function blah;select blah(field) from table where date=date;The above two commands and the select have to run before the third select runs, else the select will fail. Basically all the three commands have to run in one session.How can i do that?
Hi Greg, Thanks for the response. Is this issue only for Hive Connection? What about when i use a HUB? Can we run commands in a session there?On a different note what is the time line of the release of version 1.6? I was told that the next version of TCD will be hive database/schema aware. Is that feature in 1.6?I will send an email to the address mentioned by you to get the development link. We have huge demand for setting up TCD at Netflix and i would love try out the prototypes. Although the lack of support for Hive Databases, is a blocker for us.Thanks,Amit
Hi Amit,Unfortunately the same issue will occur for a Hive connection using the Hub. The development build should get you unblocked and also provide us with some valuable feedback.The 1.6 release has been delayed. I would expect it to be released in the later part of February. Hive in 1.6 will be database/schema aware. Again this feature is already in the development build.Regards,Stewart.
Hi,Was this issue ever solved? I saw the last communication on this thread was well over a year ago. I am still facing the same issue described in this post when I'm using Toad for Cloud eclipse plugin.. I can't seem to run a hive "script" using toad for cloud, connecting to EMR/Hive. It runs only one hive statement at a time (to clarify, not one line, but one hive statement - even if it is broken into multiple lines). this is very cumbersome when you have a bunch of settings etc for your query and you have to execute each and every single hive query one by one.. Regards,Lakshmi Naarayanan R
As Greg mentioned, a possible workaround is to use the Hive initialization statements property of the connection. Here you can add multiple valid Hive statements (intended for use as a means to initialise each connection), but note that these will all be executed each time you make a connection.Does this help you?Thanks,Lee