github.com/pingcap/tiflow@v0.0.0-20240520035814-5bf52d54e205/dm/ui/locales/en.json (about)

     1  {
     2    "add": "Add",
     3    "add event filter": "Add event filter",
     4    "add migrate rule": "Add migration rule",
     5    "add new source": "Add new source",
     6    "add source config": "Add source config",
     7    "address": "Address",
     8    "basic info": "Basics",
     9    "binlog": "binlog",
    10    "bound stage": "Bound stage",
    11    "cancel": "Cancel",
    12    "check": "Check",
    13    "cluster management": "Cluster",
    14    "confirm": "Confirm",
    15    "confirm to delete source": "Confirm to delete source",
    16    "confirm to delete task?": "Confirm to delete task?",
    17    "confirm to stop task?": "Confirm to stop task?",
    18    "consistency requirement": "Consistency",
    19    "create task": "Create Task",
    20    "create task basic info desc": "Fill in the basic information of the task, please pay attention to read the description text in each configuration.",
    21    "create task binlog_name tooltip": "Specifies the starting position of incremental replication. If there is an active/standby switchover in the upstream, GTID is necessary.",
    22    "create task data_dir tooltip": "When the task mode is \"all\" or \"full\", DM needs to first fully export the upstream data to this path on the host where the DM-worker is located. Make sure to configure it correctly and have the corresponding directory write permission and space capacity. Local absolute paths and AWS S3 are supported. When using S3, be sure to fill in the region and authentication information correctly, for example: s3://dmbucket/dump?endpoint=http://127.0.0.1:8688&access_key=s3accesskey&secret_access_key=s3secretkey&force_path_style=true&region=us-west-2.",
    23    "create task event filter ignore_event tooltip": "Select the predefined events that you want to ignore.",
    24    "create task event filter ignore_sql tooltip": "Fill in the regular expression, the matched SQL will be ignored. Multiple can be filled after carriage return.",
    25    "create task event filter name tooltip": "Fill in the filter name, English, numbers, \"-\", \"_\" are supported, and it can be unique within the task.",
    26    "create task event filters desc": "Create the event filter, which is only valid for the current task, and will be used in the next step of \"Migration Rules\" configuration.",
    27    "create task export_threads tooltip": "The number of threads for the dump unit to export data from the upstream database instance.",
    28    "create task import_threads tooltip": "The number of threads for the load unit to execute the import concurrently. The default value is 16. When there are multiple instances migrating data to TiDB at the same time, this value can be appropriately adjusted according to the load situation.",
    29    "create task meta db tooltip": "The name of the database used to store task checkpoint information. DM will use this name to create a database downstream, please ensure that the downstream database account provided in the next steps has sufficient permissions.",
    30    "create task migrate rule binlog_filter_rule tooltip": "Select the filter that needs to be matched, and the matched result will not be migrated.",
    31    "create task migrate rule desc": "Create the migration rules, migrating multiple upstream and tables to the downstream is supported.",
    32    "create task migrate rule source schema tooltip": "Select the database schema to be migrated, supports regular expressions. Or choose from the small database icons on the right.",
    33    "create task migrate rule source table tooltip": "Select the database tables to be migrated, supports regular expressions. Or choose from the small database icons on the right.",
    34    "create task migrate rule target schema tooltip": "Target database name,  keep empty if you wish to keep the original name.",
    35    "create task migrate rule target table tooltip": "Target table name,  keep empty if you wish to keep the original name.",
    36    "create task mode tooltip": "all: Automatically perform full and incremental migration. It is recommended to use when the data volume is up to terabyte, which is simple and convenient. For more than terabyte data volume , you can also consider using Lightning to complete the full migration to shorten the migration time.\n\nfull: Only perform full data migration.\n\nincremental: Only incremental data migration is performed, and the start time or binlog position needs to be specified.",
    37    "create task name tooltip": "Globally unique name, supports alphabets, numbers, \"_\" and \"-\", please do not use spaces and other special characters.",
    38    "create task repl_batch tooltip": "The number of SQL statements in a transaction batch to be replicate to the downstream database. The default value is 100, and it is recommended that it should not exceed 500 in general.",
    39    "create task repl_threads tooltip": "The number of concurrent threads the application has transferred to the local binlog. Adjusting this parameter does not affect the concurrency of upstream pulling logs.",
    40    "create task shard mode tooltip": "When there are multiple sources in a task, DM treats them as a Sharding Group to better synchronize the DDL by default. possible effects such as blocking the DDL until all sources have completed their changes.\n\n\"None\": If there is no correlation between multiple sources, this field must be set to \"None\".\n\n\"Pessimistic mode\": When an upstream sharded table executes a DDL statement, the migration of this sharded table will be suspended. After all other sharded tables execute the same DDL, the DDL will be executed in the downstream and the data migration task will restart. The advantage of this mode is that it can ensure that the data migrated to the downstream will not go wrong.\n\n\"Optimistic mode\": DM will automatically modify the DDL executed on a sharded table into a statement compatible with other sharded tables, and then migrate to the downstream. This will not block the DML migration of any sharded tables. The advantage of this mode is that it will not block data migration when processing DDL. However, improper use will cause migration interruption or even data inconsistency.",
    41    "create task source info desc": "Select the sources to be migrated that have been added. Replication config can adjust performance-related parameters, which generally no need to  modify. Incremental migration tasks need to specify the migration start position. Two methods are supported:\n1. Specify the binlog position for each upstream when creating a task. If there is a master-slave switch in the upstream, it must be filled GTID;\n2. When creating a task, leave the position blank, and select \"Create only\" at the end, then start the task in the task list and select the start time.",
    42    "create task target host tooltip": "Please fill in the connection address of the target TiDB. Domain name and IP are supported.",
    43    "create task target info desc": "Fill in the connection information of the downstream TiDB database. Please note:\n1. DM will create a metadata database downstream, please make sure that the account you fill in has the corresponding permissions;\n2. If using a domain name, please ensure that the host where the DM cluster is located has been configured properly with a DNS server;\n3. Password supports filling in plain text or using `dmctl encrypt` encrypted password string;\n4. Please check that the network firewall has opened the corresponding IP and port.",
    44    "create task target password tooltip": "Please fill in the user password of the target TiDB.",
    45    "create task target port tooltip": "Please fill in the connection port of the target TiDB.",
    46    "create task target user tooltip": "Please fill in the username of the target TiDB.",
    47    "current stage": "Stage",
    48    "dashboard loading tip": "Connecting to the monitoring component, you can change config by clicking the floating button at the bottom right corner",
    49    "dashboard professional": "Pro",
    50    "dashboard standard": "Standard",
    51    "dashboard view": "View",
    52    "data dir": "Data dir",
    53    "database": "Database",
    54    "delete": "Delete",
    55    "deleted": "Deleted!",
    56    "deleting": "Deleting...",
    57    "disable": "Disable",
    58    "disable relay": "Disable Relay Log",
    59    "disabled": "Disabled",
    60    "edit": "Edit",
    61    "edit config": "Edit config",
    62    "edit source": "Edit source",
    63    "edit task": "Edit task",
    64    "enable": "Enable",
    65    "enable gtid": "Enable GTID",
    66    "enable relay": "Enable Relay Log",
    67    "enabled": "Enabled",
    68    "event filter": "Event filter",
    69    "event filter ignore event": "Ignore event",
    70    "event filter ignore sql": "Ignore SQL",
    71    "event filter name": "Name",
    72    "event filter name is required": "Event filter name is required",
    73    "event filter name should be unique": "Event filter name should be unique",
    74    "export concurrency": "Export concurrency",
    75    "full migrate config": "Full replication config",
    76    "gtid": "GTID",
    77    "host": "Host",
    78    "host is required": "Host is required",
    79    "import concurrency": "Import concurrency",
    80    "incremental migrate config": "Incremental replication config",
    81    "incremental sync delay": "Incremental replication delay",
    82    "ip": "IP",
    83    "is enabled": "Enabled",
    84    "is leader": "Leader",
    85    "member list": "Members",
    86    "meta db": "Meta db",
    87    "migrate rules": "Migration rules",
    88    "migrate rules is required": "Migration rules are required",
    89    "migration": "Migration",
    90    "mode": "Mode",
    91    "name": "Name",
    92    "next": "Next",
    93    "no related task": "No related task",
    94    "note": "Note",
    95    "note-dashboard-config": "Please fill in the host and port of the deployed Grafana component.",
    96    "off": "Off",
    97    "on": "On",
    98    "open task by config": "Open task as plaintext config",
    99    "open task by config desc": "Create tasks directly by writing configuration files manually, suitable to copy from existing configuration files or for skilled users who want to define more detailed configurations",
   100    "open task by guide": "Open task as wizard",
   101    "open task by guide desc": "Create task through multi-step step-by-step guidance, suitable for new users and daily use",
   102    "operations": "Operations",
   103    "password": "Password",
   104    "password is required": "Password is required",
   105    "port": "Port",
   106    "port is required": "Port is required",
   107    "previous": "Previous",
   108    "refresh": "Refresh",
   109    "related task": "Related Task",
   110    "relay config (optional)": "Relay log (optional)",
   111    "relay log": "Relay log",
   112    "replication detail": "Replication Detail",
   113    "request success": "Request success",
   114    "requesting": "Requesting",
   115    "runtime config": "Runtime Config",
   116    "safe mode time duration": "Safe-Mode Duration",
   117    "safe mode time duration tooltip": "How long safe mode lasts after the task is started. This time is binlog time and not physical time. For a detailed description of Safe Mode and this configuration, please refer to the documentation",
   118    "save": "Save",
   119    "save and run": "Save and start",
   120    "search placeholder": "Search...",
   121    "second": "Seconds",
   122    "source": "Source",
   123    "source detail": "Source Detail",
   124    "source form gtid tooltip": "It is recommended to replicate by GTID(except AWS Aurora), of course the upstream needs to configure GTID first",
   125    "source form host tooltip": "Fill in the upstream connection address, support domain name or IP",
   126    "source form name tooltip": "Fill in the upstream name. Globally unique, supports alphabets, numbers, \"_\" and \"-\", does not support spaces and other special characters",
   127    "source form password tooltip": "Please fill in the user password",
   128    "source form user tooltip": "Username used to connect to the upstream database",
   129    "source info": "Source info",
   130    "source list": "Source",
   131    "source list desc": "Before creating a migration task, you need to create the upstream data source information. Please note:\n1. GTIDs. If there is a master-slave switchover, be sure to enable GTID in upstream MySQL and set GTID to True when creating the upstream, otherwise the data migration task will be interrupted during the master-slave switchover (except for AWS Aurora);\n2. Deactivate. If an upstream database needs to be temporarily offline, it can be deactivated, but other MySQL instances that are being replicated cannot perform DDL operations during the deactivation, otherwise the deactivated instance will not be able to synchronize normally after it is activated.\n3. relay log. When multiple migration tasks use the same upstream, it can put additional pressure on it. It is recommended to enable relay log to reduce the impact on upstream.",
   132    "source name": "Source name",
   133    "source name is required": "Source name is required",
   134    "source schema": "Source Database",
   135    "source table": "Source Table",
   136    "start": "Start",
   137    "start task with params": "Start with params",
   138    "start task with params desc": "The task will start according to the specified parameters, be sure to read the document about those parameters",
   139    "start task without params": "Start",
   140    "start task without params desc": "Tasks will continue to sync based on the checkpoint at the last end. If it is started for the first time, it will start at the specified location or time according to the configuration file",
   141    "start time on copy": "Start time",
   142    "start time on copy tooltip": "Synchronize all upstreams from the specified point in time, the saved location information (checkpoint) will be ignored",
   143    "status": "Status",
   144    "stop": "Stop",
   145    "stop_task list": "Stop",
   146    "submit": "Submit",
   147    "subtask": "Subtask",
   148    "sync config": "Replication config",
   149    "synchronous concurrency": "Sync concurrency",
   150    "table": "Table",
   151    "target": "Target",
   152    "target info": "Target Info",
   153    "target schema": "Target Database",
   154    "target table": "Target Table",
   155    "task detail": "Task Detail",
   156    "task list": "Task",
   157    "task list desc": "This module is used to manage data migration tasks. Before creating a new task, you need to add upstream database information on the sidebar-source configuration page. Please note:\n\nAutomatically support the source using the pt-osc/gh-ost online schema change tools without configuration; if you use other types of tools, or modified the default behavior of pt-osc/gh-ost yourself, please look for the online document for support;",
   158    "task mode": "Mode",
   159    "task name": "Name",
   160    "task name is required": "Task name is required",
   161    "task shard mode": "Shard mode",
   162    "tls config (optional)": "TLS (optional)",
   163    "transaction batch": "Transaction batch",
   164    "type": "Type",
   165    "user name": "User",
   166    "user name is required": "User name is required",
   167    "{{val}} and {{count}} others": "{{val}} and {{count}} in total",
   168    "{{val}} and {{count}} others_plural": "{{val}} and {{count}} in total"
   169  }