From dcd60e5ec6cfa2fef97e811960926ae32314d03e Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Tue, 19 Dec 2023 20:53:32 +0800 Subject: [PATCH] Update tidb-distributed-execution-framework.md Co-authored-by: Frank945946 <108602632+Frank945946@users.noreply.github.com> --- tidb-distributed-execution-framework.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/tidb-distributed-execution-framework.md b/tidb-distributed-execution-framework.md index d57508ad4bd6f..4fb6b70e762be 100644 --- a/tidb-distributed-execution-framework.md +++ b/tidb-distributed-execution-framework.md @@ -60,16 +60,10 @@ Currently, for TiDB Self-Hosted, the TiDB backend task distributed execution fra - `IMPORT INTO` is used to import data in formats such as `CSV`, `SQL`, and `PARQUET` into an empty table. For more information, see [`IMPORT INTO`](https://docs.pingcap.com/tidb/v7.2/sql-statement-import-into). -<<<<<<< HEAD -======= - - ## Limitation - The DXF can only schedule the distributed execution of one `ADD INDEX` task at a time. If a new `ADD INDEX` task is submitted before the current `ADD INDEX` distributed task has finished, the new task is executed through a transaction. - Adding indexes on columns with the `TIMESTAMP` data type through the DXF is not supported, because it might lead to inconsistency between the index and the data. - ->>>>>>> c56885347e (DXF: add a limitation that adding indexes to columns of `TIMESTAMP` data type via the DXF is not supported (#15787)) ## Prerequisites Before using the distributed framework, you need to enable the [Fast Online DDL](/system-variables.md#tidb_ddl_enable_fast_reorg-new-in-v630) mode.