Handling schema changes 

If you change a table in Cassandra after creating an external table in Hive that maps to that table in Cassandra, a runtime exception can occur. Use a workaround when changes that occur to the table in Cassandra get out of synch with the mapped table in Hive.

If you change a table in Cassandra, using CQL for example, after creating an external table in Hive that maps to that table in Cassandra, a runtime exception can occur. Changes that occur to the table in Cassandra get out of synch with the mapped table in Hive. The workaround is:

Procedure

  1. In Hive, drop the table.
    hive> drop table mytable;
  2. Run SHOW TABLES.
    hive> show tables;

    Now, the table in Hive contains the updated data.