IBM Db2 Big SQL

Problems and workarounds: Hive

Records added to a Hive table are not returned when accessing the table via a Big SQL client
After loading, inserting or otherwise populating table data directly in a Hive table, the new data is not returned when it is accessed using the Big SQL table. This is as a result of the Big SQL cache of the table not having been updated subsequent to the addition of the new data. It occurs because a latency of 20 to 30 minutes is required for the automated HCAT SYNC procedure to occur, so the Big SQL cached table has not yet been refreshed. As a workaround, you can call the HCAT_CACHE_SYNC procedure manually to refresh the Big SQL table or tables.
Hive and Db2 Big SQL catalogs are inconsistent
If Hive and Db2 Big SQL catalog tables are out of sync, you can synchronize your system in one of three ways.
Hive server 2 crashes post-Db2 Big SQL back up with error
Hive server 2 may fail after a Db2 Big SQL back up with and error from the hiveserver2.log.
Hive automatic catalog synching to Db2 Big SQL error
A Hive create table operation fails with the following DDLTask error: MetaException(message:java.lang.IllegalArgumentException: /user/bigsql/sync is not a directory.
Hive automatic catalog synching to Db2 Big SQL not working
Files for metadata changes in Hive are read from a directory on the HDFS. This directory is scanned every minute for JSON files containing metadata events, and these events are synchronized between the Db2 Big SQL catalog and the Hive catalog.
Cannot use Hive directly to work with Db2 Big SQL HBase tables
Hive is not configured with JAR files that are required by Db2 Big SQL.

Parent topic: Problems and workarounds: Hadoop and components