Hi Aniket, Yes, background monitor process is preferred in the future. And there are other places need this process already, like refreshing the caches in driver and executors. Currently, dictionary caches and index caches are refreshed by checking timestamp in every query, which introduces unnecessary overhead in query flow and impact NameNode in concurrent query scenario.
Regards, Jacky -- View this message in context: http://apache-carbondata-mailing-list-archive.1130556.n5.nabble.com/Feature-Design-Document-for-Update-Delete-support-in-CarbonData-tp3043p3237.html Sent from the Apache CarbonData Mailing List archive mailing list archive at Nabble.com.
