Consider the following sequence of operation on the same table:
- User drops it via catalog HMS api like drop_table
- User creates a table with same name
Currently #2 fails with table already exists error. This is because the table is not dropped from catalog cache after step 1.