Hive Os Driver Update

0 views

Skip to first unread message

Cora Synder

unread,

Aug 5, 2024, 10:58:11 AM8/5/24

to portsuctadas

Packagingall these dependencies in your own JAR will probably result in a massive, cluttered piece of shoftware (God, how Maven is misused nowadays). Plus, you may have compatibility issue because newer clients are not compatible with older servers. "Not compatible" meaning "unable to initialize connection with Thrift server".

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.

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.

Apache Hadoop and associated open source project names are trademarks of the Apache Software Foundation. For a complete list of trademarks, click here.

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.

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.

Linux, Unix, Mac OS X users: In a terminal session, create an SSH tunnel to the master node ofyour cluster using the following command. Replacemaster-public-dns-name with the public DNSname of the master node and path-to-key-file withthe location and file name of your Amazon EC2 private key(.pem) file.

Hi, I am using a 3rd party ETL application that I would like to connect to Hive as a datasource, using the Hive JDBC driver. Our Hive is kerberized so it needs a kerberos ticket to be able to connect. I am wondering if there is any way to automatically trigger a login from keytab when the application tries to connect to Hive. The tool itself is Java-based so I can set Java system properties when it starts, and I can also add config settings to the Hive JDBC connection string.

I've been able to get this to work by running a kinit before the process and setting -Djavax.security.auth.useSubjectCredsOnly=false, but I'd like to avoid this because it seems to be unreliable (sometimes when connecting to the DB the Java kerberos system ends up prompting for a username and password, even though the Kinit just ran, and I don't know why).

The errror - I have looked through the Jar file and this Class is in there

io.dropwizard.jersey.errors.LoggingExceptionMapper - Error handling a request: d5f34034d981f17d

java.lang.NoClassDefFoundError: Could not initialize class com.cloudera.hive.hive.core.Hive2JDBCDriver

Are you definitely choosing the receiver and not the thermostat there? The thermostat, counterintuitively, doesn't report the set point. It only talks to the receiver, which is the real brains of the operation.

The only thing the thermostat itself reports to Hubitat are its own battery voltage and the current temperature. The set point is sent to and retrieved from the receiver on the boiler. When you wake up the thermostat you'll see it can tell you the current temperature immediately, but it takes a couple of seconds to retrieve the rest of the information from the receiver.

It's actually not important, it only gives you the temperature which the thermostat sees, which is sent to the receiver and reported back to you on that device anyway, and the battery level of the thermostat itself.

So unless you're desperate to have the thermostat battery level reported in Hubitat, I wouldn't bother going through the reset and re-pairing. Though of course you could and the receiver should hook back up to the existing device just fine so long as you don't delete it.

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.

The other big reason for these changes is to better support HomeKit, which can now be used reliably with it's slightly US-centric "Off", "Cool", "Heat" and "Auto" modes, which don't account for the override capabilities of the Active Heating system.

If the system is in "Auto" mode, it is running to a schedule. Adjusting the target temperature with "Heat" or "Cool" in HomeKit configures a temporary override to that temperature until the next schedule change, at which point the system will revert to running its scheduled programming. This way people tinkering with HomeKit can't instantly mess up the operation of your heating.

The way to set a permanent override through HomeKit is to first set the system to "Off". This drops it into frost-protect mode (you can set this temperature to between 7 and 12 degrees on the thermostat). If you then choose a "Heat" or "Cool" temperature it will run this new setting permanently. Flick it to "Auto" and the programmed schedule will resume. The bracketed temperatures in "Auto" mode do nothing as this is a heat-only system, and will always revert to being the same value if set separately.

I upgraded to a C8 Hub recently and had to go through the pairing again, it took a few goes and resulted in the same devices as it did on the previous Hub. I noticed that the website with instructions looked a bit different to before and the "Step 6" referred to didn't exist?

Reset the Hive thermostat by pressing the back and menu buttons at the same time, wait for the count down and for it to restart and ask which language you would like. At this point remove the batteries to turn it off

Turn off the boiler and the boiler controller and wait for 5 seconds before turning back on. Press and hold the top button until the light on the controller is flashing pink. Press and hold the top button again until it flashes double amber.

From what I can see you've pretty much got the process, though I always start by powering off the boiler and receiver first so there's no chance of the thermostat talking back to the receiver without pairing again.

The Hive hub? If you have no other devices using it just unplug it and consign it to the drawer of Interesting Things. It may become useful again if there's some shockingly important firmware update to be installed one day, but I find that highly unlikely after all this time.

I've been giving this driver a good kicking on the test system over the past few days and it's performing well enough that I've added the controls for our real heating system to HomeKit (via Homebridge) now.

Even flinging the settings around in the Home app doesn't appear to break anything; if you set something which is unsupported (cooling, either specifically or via the "keep between" temperatures) the driver simply takes the upper (or only) requested set point temperature and uses that as both the upper and lower value, so within a few seconds the system reports the correct auto (schedule) set point and HomeKit gets updated.

The driver mimics the instruction sent by the Thermostat when requesting boost, which doesn't change the underlying operating mode. It will return to whichever mode it was in previously once the boost time has completed, and this behaviour is fixed in the Receiver's firmware. So far as I can tell there's no way to tinker with it, other than explicitly changing the mode before requesting the boost.

Answering your question in a less roundabout way; yes, if you trigger a boost from either the Thermostat or Hubitat while in schedule mode, the system will revert to schedule mode once the boost is completed.

@birdslikewires Thank you very much for your excellent driver and documentation. After reading through this forum topic I decided to go ahead and buy the thermostat and receiver and not bother with the hub at all. I've installed and paired everything up first go, and tested it out - IT works brilliantly, and if you ever get around to writing the child driver for hot water please sign me up to help with any beta testing. - Cheers!

Yes, I really must do that hot water component soon. I'm on a combi, but my test unit is the dual channel version and I've been meaning to hook it back up. Knowing it's actually going to make a difference to someone really helps with the motivation!

I've been following your work hear for a while, I have the duel channel unit aswell but I've been holding off trying your driver as I don't want to lose the hot water function of hive yet. Please could you work on the duel channel so I can finally move away from hive app and integrate with hubitat properly.

In case you weren't aware, you can continue to use the hot water function locally through your thermostat and receiver just fine, it's just that hot water won't appear in Hubitat. Switching over doesn't break the core functionality, it's just that the hot water element won't be appear in Hubitat or be controllable remotely.

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.