Hi, I have some doubts as following. Step 1: Can we only trigger to do "REPAIR INDEX ON TABLE MAIN_TABLE" by default? the system will repair the index in the background. Incremental load and compaction can return immediately, no need to wait for the repair index.
Step 2: What the lock level of the repair index command? Can we support concurrently repairing the different segments on the same table? ----- Best Regards David Cai -- Sent from: http://apache-carbondata-dev-mailing-list-archive.1130556.n5.nabble.com/
