From 50bdeba692c813c081f89cc9247f679fd60b4497 Mon Sep 17 00:00:00 2001
From: Mik Kocikowski <mkocikowski@gmail.com>
Date: Wed, 26 Mar 2014 02:01:09 -0700
Subject: [PATCH] Fixes #97, error following 'DROP TABLE'.

Following 'DROP TABLE', metadata.py was raising KeyError in line 162,
which resulted in cluster conn being terminated. Resolved this with
checking if the key (the name of the dropped table) exists.
---
 cassandra/metadata.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/cassandra/metadata.py b/cassandra/metadata.py
index 3d1814d4..655446dd 100644
--- a/cassandra/metadata.py
+++ b/cassandra/metadata.py
@@ -159,7 +159,8 @@ class Metadata(object):
 
         if not cf_results:
             # the table was removed
-            del keyspace_meta.tables[table]
+            if table in keyspace_meta.tables: 
+                del keyspace_meta.tables[table]
         else:
             assert len(cf_results) == 1
             keyspace_meta.tables[table] = self._build_table_metadata(