[CARBONDATA-3409] Fix Concurrent dataloading Issue with mv

Problem:
While performing concurrent dataloading to MV datamap, if any of the loads was not able to get TableStatusLock, then because newLoadName and segmentMap was empty, it was doing full rebuild.

Solution:
If load was not able to take tablestatuslock, then disable the datamap and return

This closes #3252

core/src/main/java/org/apache/carbondata/core/datamap/DataMapProvider.java

@@ -27,6 +27,7 @@
 import org.apache.carbondata.core.constants.CarbonCommonConstants;
 import org.apache.carbondata.core.datamap.dev.DataMapFactory;
 import org.apache.carbondata.core.datamap.status.DataMapSegmentStatusUtil;
+import org.apache.carbondata.core.datamap.status.DataMapStatusManager;
 import org.apache.carbondata.core.locks.ICarbonLock;
 import org.apache.carbondata.core.metadata.AbsoluteTableIdentifier;
 import org.apache.carbondata.core.metadata.schema.table.CarbonTable;
@@ -208,6 +209,8 @@ public boolean rebuild() throws IOException, NoSuchDataMapException {
             "Not able to acquire the lock for Table status updation for table " + dataMapSchema
                 .getRelationIdentifier().getDatabaseName() + "." + dataMapSchema
                 .getRelationIdentifier().getTableName());
+        DataMapStatusManager.disableDataMap(dataMapSchema.getDataMapName());
+        return false;
       }
     } finally {
       if (carbonLock.unlock()) {