You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/appendix/enhanced-js.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
Enhanced JS nodes allow you to utilize all built-in functions for external calls, such as networking and database operations. If your requirement is solely to process and operate on data records, it is recommended to use [standard JS nodes](standard-js.md).
4
4
5
-
For detailed instructions on how to use enhanced JS nodes and explore various scenarios, please refer to the documentation and resources available for [JS processing node](../data-transformation/process-node.md#js-process).
5
+
For detailed instructions on how to use enhanced JS nodes and explore various scenarios, please refer to the documentation and resources available for [JS processing node](../data-transformation/process-node.md#js-processing).
Copy file name to clipboardExpand all lines: docs/appendix/standard-js.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
4
4
Standard JS nodes can only process and operate on data records. If you require the usage of system built-in functions for external calls, such as networking or database operations, you can utilize [enhanced JS nodes](enhanced-js.md).
5
5
6
-
For information on how to use and scenarios, see [JS processing node](../data-transformation/process-node.md#js-process).
6
+
For information on how to use and scenarios, see [JS processing node](../data-transformation/process-node.md#js-processing).
Copy file name to clipboardExpand all lines: docs/case-practices/best-practice/raw-logs-solution.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ To enhance the efficiency of capturing data changes, TapData supports not only u
11
11
***Operating System**: Linux 64 or Windows 64 platforms.
12
12
***Storage**: Supported file systems include ext4, btrfs, zfs, xfs, sshfs; supported database block sizes are 2k, 4k, 8k, 16k, 32k.
13
13
***Port Requirements**: Some server ports must be open for service communication, including: default data transfer port: **8203**, web management default port: **8303**, raw log service port: **8190**.
14
-
***Permission**: The operating system user running the raw log plugin must have read access to redo log files; in addition to the permissions required for the source database as per the [Oracle Preparation Work](../../connectors/on-prem-databases/oracle.md#source) and enabling archive logs, additional permissions must be granted to simulate Oracle's data information structure and processes to cache part of Oracle Schema information to support the parsing of redo logs.
14
+
***Permission**: The operating system user running the raw log plugin must have read access to redo log files; in addition to the permissions required for the source database as per the [Oracle Preparation Work](../../connectors/on-prem-databases/oracle.md#as-a-source-database) and enabling archive logs, additional permissions must be granted to simulate Oracle's data information structure and processes to cache part of Oracle Schema information to support the parsing of redo logs.
Copy file name to clipboardExpand all lines: docs/connectors/on-prem-databases/sqlserver.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,6 +59,7 @@ In addition, for synchronization from SQL Server to PostgreSQL, extra support is
59
59
* When SQL Server is used as the source database and a DDL operation (such as adding a column) is performed on the fields of a table under incremental sync, you will need to restart change data capture for the table to avoid data synchronization errors or failures.
60
60
61
61
<details>
62
+
62
63
<summary>Restart change data capture for the corresponding table</summary>
63
64
64
65
```sql
@@ -342,8 +343,11 @@ When configuring SQL Server as the source node for a task, TapData provides seve
342
343
**A**: SQL Server 2005 does not support CDC. Incremental data capture can be done via [field polling](../../introduction/change-data-capture-mechanism.md), or by using the following method:
343
344
344
345
<details>
346
+
345
347
<summary>SQL Server 2005 as a Source Solution</summary>
348
+
346
349
Since CDC is supported from SQL Server 2008 onward, for earlier versions, you can simulate change data capture using Custom SQL. When replicating data from older versions, the source table must have a change-tracking column, such as <b>LAST_UPDATED_TIME</b>, which is updated with every insert or update. When creating the data replication task, set the task synchronization type to <b>Full</b>, enable <b>Repeat Custom SQL</b> as <b>True</b>, and provide appropriate Custom SQL in the mapping design.
350
+
347
351
</details>
348
352
349
353
* **Q**: When certain tables cannot enable CDC while others work normally. How can I resolve this issue without restarting the entire database?
Copy file name to clipboardExpand all lines: docs/connectors/on-prem-databases/tidb.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -165,6 +165,6 @@ GRANT SELECT, INSERT, UPDATE, DELETE, ALTER, CREATE, DROP ON *.* TO 'username';
165
165
166
166
1. Extract the downloaded file, then navigate to the extracted directory and run the `make` command to compile.
167
167
168
-
2. Locate the generated **cdc** binary file and place it in the **{tapData-dir}/run-resource/ti-db/tool** directory on the TapData engine machine (replace if necessary).
168
+
2. Locate the generated **cdc** binary file and place it in the **\{tapData-dir\}/run-resource/ti-db/tool** directory on the TapData engine machine (replace if necessary).
169
169
170
170
3. Use the `chmod` command to grant read, write, and execute permissions to the files in this directory.
| Task Sync Type Check | 【ERROR】【2023-01-01 00:00:00】【Task Sync Type Check】【Node-Source】The sync type (Full) of this node does not match the task sync type (Full + Incremental), the task cannot start normally, please check the relevant configuration. |
18
18
| Default Timezone Check | 【WARN】【2023-01-01 00:00:00】【Default Timezone Check】The default timezone connected by the source node (Node-Source) is inconsistent with the default timezone connected by the target node (Node-Target), which may cause inconsistency in synchronized data. |
19
-
| Task Model Inference Check | 【ERROR】【2023-01-01 00:00:00】【Task Model Inference Check】Task configuration model inference failed, the task cannot start normally, please check the relevant issues. <br /> { <br />Node Name 1: Table Name 1: Field Name 1; <br />Node Name 2: Table Name 2: Field Name 2 <br />}|
19
+
| Task Model Inference Check | 【ERROR】【2023-01-01 00:00:00】【Task Model Inference Check】Task configuration model inference failed, the task cannot start normally, please check the relevant issues. <br /> { <br />Node Name 1: Table Name 1: Field Name 1; <br />Node Name 2: Table Name 2: Field Name 2 <br />}|
| Source Connection Status Check | 【ERROR】【2023-01-01 00:00:00】【Source Connection Status Check】【Node-Source】The data connection of this node is unavailable, the task cannot start normally, please check the relevant issues. { Data source login permission check failed: Wrong username or password }|
26
-
| Source Model Load Check | 【ERROR】【2023-01-01 00:00:00】【Source Model Load Check】【Node-Source】The data model loading of this node failed, the task cannot start normally, please check the relevant issues. <br />{ Table Name 1; <br />Table Name 2 <br />}|
25
+
| Source Connection Status Check | 【ERROR】【2023-01-01 00:00:00】【Source Connection Status Check】【Node-Source】The data connection of this node is unavailable, the task cannot start normally, please check the relevant issues. { Data source login permission check failed: Wrong username or password }|
26
+
| Source Model Load Check | 【ERROR】【2023-01-01 00:00:00】【Source Model Load Check】【Node-Source】The data model loading of this node failed, the task cannot start normally, please check the relevant issues. <br />{ Table Name 1; <br />Table Name 2 <br />}|
27
27
| Source Type Mapping Check | 【WARN】【2023-01-01 00:00:00】【Source Type Mapping Check】【Node-Source】【Personinfo】【id】The data type of this field is temporarily unsupported, and will be ignored during data reading. |
| Target Connection Status Check | 【ERROR】【2023-01-01 00:00:00】【Target Connection Status Check】【Node-Target】The data connection of this node is unavailable, the task cannot start normally, please check the relevant issues. { Data source login permission check failed: Wrong username or password }|
34
-
| Target Model Load Check | 【ERROR】【2023-01-01 00:00:00】【Target Model Load Check】【Node-Target】The data model loading of this node failed, the task cannot start normally, please check the relevant issues. { Table Name 1; Table Name 2 }|
33
+
| Target Connection Status Check | 【ERROR】【2023-01-01 00:00:00】【Target Connection Status Check】【Node-Target】The data connection of this node is unavailable, the task cannot start normally, please check the relevant issues. { Data source login permission check failed: Wrong username or password }|
34
+
| Target Model Load Check | 【ERROR】【2023-01-01 00:00:00】【Target Model Load Check】【Node-Target】The data model loading of this node failed, the task cannot start normally, please check the relevant issues. { Table Name 1; Table Name 2 }|
35
35
| Target Type Mapping Failure | 【WARN】【2023-01-01 00:00:00】【Target Type Mapping Check】【Node-Target】【Personinfo】【id】The data type of this field is temporarily unsupported, and will be ignored during data writing. |
36
36
| Target Type Mapping Warning | 【WARN】【2023-01-01 00:00:00】【Source Type Mapping Check】【Node-Target】【Personinfo】【pic】The target data type mapped by this field is a system-guessed result, which may be biased. Please check and confirm whether it meets the expectations, and adjust accordingly. |
37
37
@@ -41,4 +41,4 @@ After the data replication/development task configuration is completed, execute
| Source Node | MariaDB Timezone Check | 【WARN】【2023-01-01 00:00:00】【MariaDB Timezone Check】【Node-MariaDB】The timezone setting in the MariaDB connection configuration only takes effect in the Full phase and is invalid in the Incremental phase. |
43
43
| Target Node | Oracle NOT NULL Constraint Check | 【WARN】【2023-01-01 00:00:00】【Oracle NOT NULL Constraint Check】【Node-Oracle】【Personinfo】【id】When writing NOT NULL fields with Oracle data source as the target, "" cannot be processed. |
44
-
| Target Node | CK Primary Key Type Check | 【WARN】【2023-01-01 00:00:00】【CK Primary Key Type Check】【Node-CK】【Personinfo】When using ClickHouse data source as the target and the primary key data type is floating-point, this data table does not support the processing of update delete events. |
44
+
| Target Node | CK Primary Key Type Check | 【WARN】【2023-01-01 00:00:00】【CK Primary Key Type Check】【Node-CK】【Personinfo】When using ClickHouse data source as the target and the primary key data type is floating-point, this data table does not support the processing of update delete events. |
0 commit comments