Download UPDATED Hive Driver
Vaun Stokes
The Cloudera JDBC Driver for Hive enables your enterprise users to access Hadoop data through Business Intelligence (BI) applications with JDBC support. The driver achieves this by translating calls from the application into SQL and passing the SQL queries to the underlying Hive engine.
For a standalone install the Cloudera driver may be a good solution - registration just means leaving one of your "junk" e-mails to get a couple of marketing messages (and you can un-subscribe then). Although I admit I've never used it on a non-Cloudera cluster.
You can use popular business intelligence tools like Microsoft Excel, MicroStrategy,QlikView, and Tableau with Amazon EMR to explore and visualize your data. Many of these toolsrequire Java Database Connectivity (JDBC) driver or an Open Database Connectivity (ODBC) driver.Amazon EMR supports both JDBC and ODBC connectivity.
Before you install and work with SQL Workbench/J, download the driver package and install the driver. The drivers included in the package support the Hive versions available in Amazon EMR release versions 4.0 and later. For detailed release notes and documentation, see the PDF documentation included in the package.
When you return to the Select Connection Profile dialog box, verify thatthe Driver field is set to Hive JDBC andprovide the following JDBC connection string in the URL field: jdbc:hive2://localhost:10000/default.
When the connection is established you will see errors in the log console and might get a warning that the driver is not JDBC 3.0 compatible. These alerts are due to yet-to-be-implemented parts of the JDBC metadata API and can safely be ignored. To test the connection enter SHOW TABLES in the console and click the run icon.
Learn how to use the JDBC driver from a Java application. To submit Apache Hive queries to Apache Hadoop in Azure HDInsight. The information in this document demonstrates how to connect programmatically, and from the SQuirreL SQL client.
There are multiple implementations of storage systems which utilize Hive on the server-side - including Apache Spark, Impala, etc. Most of them support the standard Hive JDBC driver which is used in DBeaver to communicate with the server.
DBeaver uses a so-called Hive JDBC Uber Jar driver ( -jdbc-uber-jar) which includes all necessary dependencies. You do not need to download anything - DBeaver will download everything automatically (if you have internet access).
Hi @birdslikewires - huge thanks for developing these Hive drivers and for posting all the tips along the way!! I'm all setup and HE has paired with the receiver (single channel/heat only) and the thermostat devices. However, I don't see how to interact with the devices. I've tried using the Thermostat Controller HE app, but get this error when adding the Hive Receiver: Error: Cannot invoke method capitalize() on null object
There's a bug I'm yet to resolve which I only found myself yesterday, as I took the plunge and finally switched the receiver which runs my boiler over to this driver. For some reason it's not configuring correctly and I'll need to find some time to investigate.
I don't know anything about the various apps that may be able to interact with the driver; I was doing this purely to ditch the Hive hub while still having a means of monitoring the boiler's activity. As I figure things out I'll certainly post back though!
Okay, check again for a driver update. Once it's installed, go to your receiver driver with the type "Hive Receiver SLR1" and hit Configure. If it's not there already it'll create (or update) a child driver of the type "Hive Receiver SLR1 Heating".
Yes, @birdslikewires thanks so much for the quick update - Success also here! I updated the drivers with HPM and am now able to use a virtual switch to change the Heating Setpoint to different values - great so far! I couldn't get the built in Thermostat Controller app to work, however, so I started to build my own workflow. With Rule Machine, I can now control the boiler all the way from HomeKit > Virtual Thermostat > Hive Receiver - AWESOME! However, I am now trying to get the Virtual Thermostat to update when the physical thermostat is adjusted. I can't get the RM triggers to see the values in the Receiver attributes... Apologies if I'm making a dumb mistake, this is the first time I'm doing this level of work in HE. Thanks in advance, and if this isn't possible, then I'll be very happy with the level of control you've given me so far!!! Log screenshot below showing how the one rule works, but then how the reverse rule isn't being triggered. THANKS IN ADVANCE!
Screen Shot 2023-08-21 at 12.04.181410482 89.7 KB
Screen Shot 2023-08-21 at 12.09.401384692 72.6 KB
Very odd. I'm on HE v2.3.5.152 in case there's been some bug fixed in Rule Machine. If you're able to get by I'll keep tinkering with the driver and hopefully some update that happens in the future irons things out!
Updated the Receiver parent and child drivers to v0.69. There are some breaking changes here regarding the removal of the heatingMode custom attribute (which was unreliable) and the renaming of heatingBoostRemaining to overrideMinutes with an eye on hot water being added.
Developers can use Hive JDBC Driver to rapidly build Web, Desktop, and Mobile applications that interact with live data from Hive.The Apache Hive Driver has the same JDBC architecture as the JDBC drivers for MySQLand OLEDB, including Connection, Statement and ResultSet objects. Because ofthis you can now access Hive data in an easy, familiar way.You can use the Apache Hive Driver throughpopular IDEs (Eclipse, IntelliJ, NetBeans, etc.), in code through familiar classes, and in data controls availablethrough Swing, Eclipse SWT Widgets, etc.
Our drivers undergo extensive testing and are certified to be compatible with leading analytics and reporting applications like SAP Crystal Reports, Pentaho, Business Objects, Crystal Reports and many more.
The CData JDBC drivers include powerful fully-integrated remoting capabilitiesthat makes Apache Hive data accessible from virtually anywhere. The driversinclude the optional ability to accept incoming SQL and MySQL client connections and servicestandard database requests.
With the CData JDBC drivers, users can interact with Apache Hive data from any clientthat supports SQL Server or MySQL: from web & mobile applications, to CRM and CMS systems, BI toolslike SQL Server Analysis Services, and even through popular management applications like MySQL Workbench.
The Apache Hive JDBC Driver offers the most natural way to access Hive data from anyJava/J2EE application. Simply use the Apache Hive Driver to connect and access data just as youwould access any traditional database. The driver is completely self-contained - no additional softwareinstallation is required!
The Apache Hive Driver has the same JDBC architecture as the JDBC drivers for MySQLand OLEDB, including Connection, Statement and ResultSet objects. Because ofthis you can now access Hive data in an easy, familiar way.You can use the Apache Hive Driver throughpopular IDEs (Eclipse, IntelliJ, NetBeans, etc.), in code through familiar classes, and in data controls availablethrough Swing, Eclipse SWT Widgets, etc.
Support is provided for the template as downloaded from the Marketplace, without changes to the way it works. These drivers are designed to only work with Collibra Catalog and cannot be used for other purposes.
For our other drivers we have similar driver custom parameters available: UseProxy, ProxyHost, ProxyPort, ProxyUID, ProxyPWD; However, information is very limited unfortunately and I don't have an instance with this config to test against.
If you check within the connectors folder, Default location:
C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\hive\lib
you can see that the driver is developed by Simba, so you may want to check the Simba community to see if there are passable parameters other than what I've posted.
... ... ...
but never have the solution for supporting the jdbc://hive(not 2),
I supposed that only jdbc:hive but not jdbc:hive2 would be worked.
so maybe the root cause is "org.apache.hive.jdbc",
im new in Clojure and failed to rebuild spark deps,
how can i use "org.apache.hadoop.hive.jdbc" instead?
or can we build a new plugin for older hive,
or support two kind of protocol on the same driver like this:
Hive has no official ODBC drivers since version 3 at least. All Hadoop distributions (and Microsoft) distribute the ODBC driver from Simba. It works OK if you can use native queries (the driver passes the query as-is to Hive) or if you query is simple. Otherwise, the driver tries to be smart and fails miserably.
As I am neither a customer of Simba nor of Hortonworks, I cannot send a bug report. I asked on the Hortonworks community, but I feel quite isolated. I will share here a few of my experience, and hopefully, a good soul might pop by and tell me what I am doing wrong (or join me in whinging about this driver).
You will get that one a lot. Basically, on any error, this is what you will get, with the place of the error being your first question mark. I thought for a long time that the driver was completely borked, but actually no (just majorly, not completely). If you enable logging (LogLevel=4 and eg. LogPath=/tmp/hivelogs) in your obcinst.ini you will be able to see the inner error, which is a lot more informative.
My guess is that the driver mixes up with unix_timestamp(), with no parameters, which is deprecated. As a workaround, you can cast your date as bigint, which works the same. I was proud of myself with this workaround, but look below (Cast) for the issues this causes.
This one surprises me because a simple query (select floor(42)) will succeed, whereas the same line use in a more complex query will give fail. I see from the logs that the driver shows the error but is somehow able to recover for simple queries, not for complex queries.
df19127ead