tree 6933a7ae66948302e73875b2ea68dcd318e91400
parent 310b06de1d2df88a78cbf005ca09f08553c98539
author kunal642 <kunalkapoor642@gmail.com> 1518463411 +0530
committer manishgupta88 <tomanishgupta18@gmail.com> 1519450154 +0530

[CARBONDATA-2142] [CARBONDATA-1763] Fixed issues while creation concurrent datamaps

Analysis:
1. GenerateTableSchemaString in CarbonMetastore did not have any specific implementation for hive metastore due to which carbontables were being
cached in MetaData. As there is no way to refresh table in hivemetastore therefore this is wrong. All queries should get the latest carbon table
from metastore and not from cache.
2. If updating the main table status fails then revertMainTableChanges method is called to revert the changes. The logic to revert was wrong which led
to wrong entry getting deleted from the schema.
3. Moved the force remove logic before taking locks as deletion from metastore should happen even if the lock if not present as the table is in
stale state(Entry is not there in parent but available in metastore).

This closes #1975