The Hive JDBC client can run in two different modes: standalone and embedded.
Standalone mode is where the client connects to a separate standalone HiveServer by specifying the host:port of the server in the jdbc URL like this: jdbc:hive://localhost:10000/default. In this case the hive configs are not needed by the client, since the client is making thrift requests to the server which has the Hive configs. the Hive Server knows how to resolve the metastore. Embedded mode is where the JDBC client "connects to itself" so to speak using a JDBC url like this: jdbc:hive://. It's as if the client is running an embedded server that only it communicates with. In this case the client needs the Hive configs since it needs to resolve the metastore, amongst other things. The metastore dependency in this case is what will cause you to see jpox errors appear if those jars aren't found. HTH, Bill On Tue, Oct 20, 2009 at 4:14 AM, Arijit Mukherjee <ariji...@gmail.com>wrote: > BTW - the service is working though, in spite of those exceptions. I'm > able to run queries and get results. > > Arijit > > 2009/10/20 Arijit Mukherjee <ariji...@gmail.com>: > > I created a hive-site.xml using the outline given in the Hive Web > > Interface tutorial - now that file is in the classpath of the Web > > Service - and the service can find the file. But, now there's another > > exception - > > > > 2009-10-20 14:27:30,914 DEBUG [httpSSLWorkerThread-14854-0] > > HiveQueryService - connecting to Hive using URL: > > jdbc:hive://localhost:10000/default > > 2009-10-20 14:27:30,969 DEBUG [httpSSLWorkerThread-14854-0] > > Configuration - java.io.IOException: config() > > at > org.apache.hadoop.conf.Configuration.<init>(Configuration.java:176) > > at > org.apache.hadoop.conf.Configuration.<init>(Configuration.java:164) > > at org.apache.hadoop.hive.conf.HiveConf.<init>(HiveConf.java:287) > > at > org.apache.hadoop.hive.jdbc.HiveConnection.<init>(HiveConnection.java:63) > > at > org.apache.hadoop.hive.jdbc.HiveDriver.connect(HiveDriver.java:109) > > at java.sql.DriverManager.getConnection(DriverManager.java:582) > > at java.sql.DriverManager.getConnection(DriverManager.java:185) > > at > com.ctva.poc.hive.service.HiveQueryService.getConnection(HiveQueryService.java:134) > > at > com.ctva.poc.hive.service.HiveQueryService.connectDB(HiveQueryService.java:43) > > > > Apparently, something goes wrong during the config routine. Do I need > > something more within the service? > > > > Regards > > Arijit > > > > 2009/10/20 Arijit Mukherjee <ariji...@gmail.com>: > >> Hi > >> > >> I'm trying to create a Web Service which will access Hive (0.4.0 > >> release) using JDBC. I used to sample JDBC code from the wiki > >> ( > http://wiki.apache.org/hadoop/Hive/HiveClient#head-fd2d8ae9e17fdc3d9b7048d088b2c23a53a6857d > ), > >> but when I'm trying to connect the the DB using the DriverManager, > >> there's an exception which seems to relate to hive-site.xml (HiveConf > >> - hive-site.xml not found.). But I could not find any hive-site.xml in > >> $HIVE_HOME/conf - there's only hive-default.xml. The wiki page also > >> speaks about couple of jpox JAR files, which aren't in the lib folder > >> either. > >> > >> Am I missing something here? > >> > >> Regards > >> Arijit > >> > >> -- > >> "And when the night is cloudy, > >> There is still a light that shines on me, > >> Shine on until tomorrow, let it be." > >> > > > > > > > > -- > > "And when the night is cloudy, > > There is still a light that shines on me, > > Shine on until tomorrow, let it be." > > > > > > -- > "And when the night is cloudy, > There is still a light that shines on me, > Shine on until tomorrow, let it be." >
