C
CK
Guest
Hi, as discussed in case 00357638 and earlier conversations with support and dev team: The embedding application should not need to manage the driver cache of the Cassandra JDBC driver. As of v6.0 the *embedding*application* needs to make sure that the Cassandra Driver updates its metadata cache: for any Cassandra objects created after the initial metadata cache setup, the application must explicitly call REFRESH_MAP before any such new Cassandra tables/columns can be accessed. Suggestion: In case the driver hits a missing table or missing column (not present in metadata cache), the driver should reach out to the Cassandra database and double-check whether the table/column is really missing. If the table/column exists on the database, the driver should update its metadata cache instead of throwing a table-not-found-exception. In case of static environments with critical response time requirements, this automatic update should be made optional. Thanks for considering, Christian
Continue reading...
Continue reading...