Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Violates not-null constraint #648

Open
lephuhai opened this issue Mar 11, 2021 · 14 comments
Open

Violates not-null constraint #648

lephuhai opened this issue Mar 11, 2021 · 14 comments
Labels
help wanted Extra attention is needed

Comments

@lephuhai
Copy link

lephuhai commented Mar 11, 2021 •
edited
Loading

Your command: pipelinewise run_tap --tap mysql_web_warehouse --target postgres_dwh

Why tap-mysql create a new column to target-postgres and foreign key always Null value?

Your question
image

And after the data source is updated, I re-run the pipeline again, and then it throws an error: violates not-null constraint.
Please help me fix this issue.

Details exception:

time=2021-03-11 07:16:18 logger_name=pipelinewise log_level=INFO message=Profiling mode not enabled
time=2021-03-11 07:16:18 logger_name=pipelinewise.cli.pipelinewise log_level=INFO message=Running mysql_web_warehouse tap in postgres_dwh target
time=2021-03-11 07:16:18 logger_name=pipelinewise.cli.pipelinewise log_level=INFO message=No table available that needs to be sync by fastsync
time=2021-03-11 07:16:18 logger_name=pipelinewise.cli.pipelinewise log_level=INFO message=Table(s) selected to sync by singer: ['pushsale-advertisers', 'pushsale-leads', 'pushsale-leads_meta', 'pushsale-offers', 'pushsale-opportunities', 'pushsale-opportunity_attributes', 'pushsale-orders', 'pushsale-users']
time=2021-03-11 07:16:18 logger_name=pipelinewise.cli.commands log_level=INFO message=Writing output into /root/.pipelinewise/postgres_dwh/mysql_web_warehouse/log/postgres_dwh-mysql_web_warehouse-20210311_071618.singer.log
time=2021-03-11 07:16:19 logger_name=pipelinewise.cli.pipelinewise log_level=ERROR message=Command failed. Return code: 1
Error(s) found:
psycopg2.errors.NotNullViolation: null value in column "id_20210311_0438" violates not-null constraint

Full log: /root/.pipelinewise/postgres_dwh/mysql_web_warehouse/log/postgres_dwh-mysql_web_warehouse-20210311_071618.singer.log.failed
Traceback (most recent call last):
  File "/app/pipelinewise/pipelinewise/cli/pipelinewise.py", line 1035, in run_tap
    stream_buffer_size=stream_buffer_size)
  File "/app/pipelinewise/pipelinewise/cli/pipelinewise.py", line 869, in run_tap_singer
    commands.run_command(command, self.tap_run_log_file, update_state_file)
  File "/app/pipelinewise/pipelinewise/cli/commands.py", line 365, in run_command
    raise RunCommandException(f'Command failed. Return code: {proc_rc}\n'
pipelinewise.cli.commands.RunCommandException: Command failed. Return code: 1
Error(s) found:
psycopg2.errors.NotNullViolation: null value in column "id_20210311_0438" violates not-null constraint

Full log: /root/.pipelinewise/postgres_dwh/mysql_web_warehouse/log/postgres_dwh-mysql_web_warehouse-20210311_071618.singer.log.failed
time=2021-03-11 07:16:19 logger_name=pipelinewise.cli.pipelinewise log_level=INFO message=
-------------------------------------------------------
TAP RUN SUMMARY
-------------------------------------------------------
    Status  : FAILED
    Runtime : 0:00:00.941220
-------------------------------------------------------
@lephuhai lephuhai added the help wanted Extra attention is needed label Mar 11, 2021
@Samira-El
Copy link
Contributor

Hey,

I'm not sure I'm understanding your questions, but I'll try.

re the columns id_20210311_0438 and group_id_20210311_0438, this is column versioning which happens when the columns in the source (in your case, mysql table) changes their type. Read more here: https://transferwise.github.io/pipelinewise/user_guide/schema_changes.html

re psycopg2.errors.NotNullViolation: null value in column "id_20210311_0438" violates not-null constraint
It simply means that target-postgres has received a new record to insert where the value in id_20210311_0438 column that already exists.
Try to resync with FastSync pipelinewise --tap mysql_web_warehouse --target postgres_dwh sync_table --tables pushsale-users

@lephuhai
Copy link
Author

lephuhai commented Mar 11, 2021 •
edited
Loading

Dear @Samira-El ,

Follow your instruction, I keep going to run command sync_tables like this:

$ pipelinewise sync_tables --target postgres_dwh --tap mysql_web_warehouse --tables pushsale.users

And everything from our data is correct. ❤️
image

Keep thing about that, I updated the data source in the MySQL database and run the pipeline again and got an exception, and the data become the incorrect schema.

$ pipelinewise run_tap --tap mysql_web_warehouse --target postgres_dwh

image

(pipelinewise) root@pipelinewise-588d944fb8-qt5z2:~/.pipelinewise/postgres_dwh/mysql_web_warehouse# pipelinewise run_tap --tap mysql_web_warehouse --target postgres_dwh
time=2021-03-11 08:56:09 logger_name=pipelinewise log_level=INFO message=Profiling mode not enabled
time=2021-03-11 08:56:09 logger_name=pipelinewise.cli.pipelinewise log_level=INFO message=Running mysql_web_warehouse tap in postgres_dwh target
time=2021-03-11 08:56:09 logger_name=pipelinewise.cli.pipelinewise log_level=INFO message=No table available that needs to be sync by fastsync
time=2021-03-11 08:56:09 logger_name=pipelinewise.cli.pipelinewise log_level=INFO message=Table(s) selected to sync by singer: ['pushsale-advertisers', 'pushsale-leads', 'pushsale-leads_meta', 'pushsale-offers', 'pushsale-opportunities', 'pushsale-opportunity_attributes', 'pushsale-orders', 'pushsale-users']
time=2021-03-11 08:56:09 logger_name=pipelinewise.cli.commands log_level=INFO message=Writing output into /root/.pipelinewise/postgres_dwh/mysql_web_warehouse/log/postgres_dwh-mysql_web_warehouse-20210311_085609.singer.log
time=2021-03-11 08:56:11 logger_name=pipelinewise.cli.pipelinewise log_level=ERROR message=Command failed. Return code: 1
Error(s) found:
psycopg2.errors.NotNullViolation: null value in column "id_20210311_0856" violates not-null constraint

Full log: /root/.pipelinewise/postgres_dwh/mysql_web_warehouse/log/postgres_dwh-mysql_web_warehouse-20210311_085609.singer.log.failed
Traceback (most recent call last):
  File "/app/pipelinewise/pipelinewise/cli/pipelinewise.py", line 1035, in run_tap
    stream_buffer_size=stream_buffer_size)
  File "/app/pipelinewise/pipelinewise/cli/pipelinewise.py", line 869, in run_tap_singer
    commands.run_command(command, self.tap_run_log_file, update_state_file)
  File "/app/pipelinewise/pipelinewise/cli/commands.py", line 365, in run_command
    raise RunCommandException(f'Command failed. Return code: {proc_rc}\n'
pipelinewise.cli.commands.RunCommandException: Command failed. Return code: 1
Error(s) found:
psycopg2.errors.NotNullViolation: null value in column "id_20210311_0856" violates not-null constraint

Full log: /root/.pipelinewise/postgres_dwh/mysql_web_warehouse/log/postgres_dwh-mysql_web_warehouse-20210311_085609.singer.log.failed
time=2021-03-11 08:56:11 logger_name=pipelinewise.cli.pipelinewise log_level=INFO message=
-------------------------------------------------------
TAP RUN SUMMARY
-------------------------------------------------------
    Status  : FAILED
    Runtime : 0:00:01.200733
-------------------------------------------------------

I always keep to trying run run_tap command into crontab, but destination data is going wrong and exception process.
Follow into documentation from here: https://transferwise.github.io/pipelinewise/user_guide/scheduling.html#

@lephuhai
Copy link
Author

FastSync command: pipelinewise sync_tables --target postgres_dwh --tap mysql_web_warehouse
FastSync have an warning: Incorrect datetime value

/app/pipelinewise/pipelinewise/fastsync/mysql_to_postgres.py:99: Warning: (1411, "Incorrect datetime value: '0000-00-00 00:00:00' for function str_to_date")
  mysql.copy_table(table, filepath)
time=2021-03-11 09:37:10 logger_name=pipelinewise.fastsync.mysql_to_postgres log_level=INFO message=
        -------------------------------------------------------
        SYNC FINISHED - SUMMARY
        -------------------------------------------------------
            Total tables selected to sync  : 8
            Tables loaded successfully     : 8
            Exceptions during table sync   : []

            Pool size                      : 1
            Runtime                        : 0:00:59.075908
        -------------------------------------------------------

@lephuhai
Copy link
Author

My tap-mysql configure like this, please help some ideas to find out the problem @Samira-El

---

id: "mysql_web_warehouse"                     # Unique identifier of the tap
name: "web_warehouse MySQL Database"          # Name of the tap
type: "tap-mysql"                      # !! THIS SHOULD NOT CHANGE !!
owner: "[email protected]"              # Data owner to contact
db_conn:
  host: "mysql"                       # MySQL/ MariaDB host
  port: 3306                           # MySQL/ MariaDB port
  user: "root"                       # MySQL/ MariaDB user
  password: "password"               # Plain string or vault encrypted
  dbname: "pushsale"                  # MySQL/ MariaDB database name
target: "postgres_dwh"                    # ID of the target connector where the data will be loaded
batch_size_rows: 20000                 # Batch size for the stream to optimise load performance
stream_buffer_size: 0                  # In-memory buffer size (MB) between taps and targets for asynchronous data pipes
schemas:
  - source_schema: "pushsale"             # Source schema (aka. database) in MySQL/ MariaDB with tables
    target_schema: "public"        # Target schema in the destination Data Warehouse
    target_schema_select_permissions:  # Optional: Grant SELECT on schema and tables that created
      - developer
    tables:
      - table_name: "advertisers"
        replication_method: "LOG_BASED"
      - table_name: "offers"
        replication_method: "LOG_BASED"
      - table_name: "leads"
        replication_method: "LOG_BASED"
      - table_name: "leads_meta"
        replication_method: "LOG_BASED"
      - table_name: "users"
        replication_method: "LOG_BASED"
      - table_name: "opportunities"
        replication_method: "LOG_BASED"
      - table_name: "opportunity_attributes"
        replication_method: "LOG_BASED"
      - table_name: "orders"
        replication_method: "LOG_BASED"

@lephuhai
Copy link
Author

I did clear all binlog before running the command:
pipelinewise run_tap --tap mysql_web_warehouse --target postgres_dwh

but it's doesn't work well. The column name always has a time suffix.
image

@Samira-El
Copy link
Contributor

what's the column type of ID and group_id in your mysql table?

@lephuhai
Copy link
Author

Detailed table information in MySQL is
image

@lephuhai
Copy link
Author

Are you have any solution to debug this case? Or something wrong with my configure @Samira-El

@lephuhai
Copy link
Author

Can you help me to debug this issue? @Samira-El

@Samira-El
Copy link
Contributor

Hey,

Can you also share the detailed table information in of this table in postgres?

@lephuhai
Copy link
Author

lephuhai commented Mar 16, 2021 •
edited
Loading

Dear @Samira-El,

My user table in Postgres:

image

And detailed value is Postgres:

image

@lephuhai
Copy link
Author

In the process Pipelinewise run_tap, I checked my destination database and the table columns inserted are correct. And after the pipeline is finished. I re-check and it's wrong like the problem I described above.

Logging information from Pipelinewise:

time=2021-03-16 03:18:46 logger_name=pipelinewise log_level=INFO message=Profiling mode not enabled
time=2021-03-16 03:18:46 logger_name=pipelinewise.cli.pipelinewise log_level=INFO message=Running mysql_web_warehouse tap in postgres_dwh target
time=2021-03-16 03:18:46 logger_name=pipelinewise.cli.pipelinewise log_level=INFO message=Table(s) selected to sync by fastsync: ['pushsale-advertisers', 'pushsale-leads', 'pushsale-leads_meta', 'pushsale-offers', 'pushsale-opportunities', 'pushsale-opportunity_attributes', 'pushsale-orders', 'pushsale-tests', 'pushsale-users']
time=2021-03-16 03:18:46 logger_name=pipelinewise.cli.commands log_level=INFO message=Writing output into /root/.pipelinewise/postgres_dwh/mysql_web_warehouse/log/postgres_dwh-mysql_web_warehouse-20210316_031846.fastsync.log
time=2021-03-16 03:18:47 logger_name=pipelinewise.cli.pipelinewise log_level=INFO message=Table(s) selected to sync by singer: ['pushsale-advertisers', 'pushsale-leads', 'pushsale-leads_meta', 'pushsale-offers', 'pushsale-opportunities', 'pushsale-opportunity_attributes', 'pushsale-orders', 'pushsale-tests', 'pushsale-users']
time=2021-03-16 03:18:47 logger_name=pipelinewise.cli.commands log_level=INFO message=Writing output into /root/.pipelinewise/postgres_dwh/mysql_web_warehouse/log/postgres_dwh-mysql_web_warehouse-20210316_031846.singer.log
time=2021-03-16 03:22:51 logger_name=pipelinewise.cli.pipelinewise log_level=INFO message=
-------------------------------------------------------
TAP RUN SUMMARY
-------------------------------------------------------
    Status  : SUCCESS
    Runtime : 0:04:04.981012
-------------------------------------------------------

In fact, for one pipelinewise run_tap. We have 2 log files:

  1. postgres_dwh-mysql_web_warehouse-20210316_031846.fastsync.log.success
  2. postgres_dwh-mysql_web_warehouse-20210316_031846.singer.log.success

With what I did, Do you think I am configuring something wrong? @Samira-El

@lephuhai
Copy link
Author

Singer always tries to create a table but it exists because fastsync created 😮
And singer do versioning my column?

(pipelinewise) root@pipeline-sync-7f478894f-444qc:~/.pipelinewise/postgres_dwh/mysql_web_warehouse/log# cat postgres_dwh-mysql_web_warehouse-20210316_071827.singer.log.success
time=2021-03-16 07:19:29 logger_name=tap_mysql log_level=INFO message=Server Parameters: version: 5.7.33-log, wait_timeout: 28800, innodb_lock_wait_timeout: 3600, max_allowed_packet: 67108864, interactive_timeout: 28800
time=2021-03-16 07:19:29 logger_name=tap_mysql log_level=INFO message=Server SSL Parameters(blank means SSL is not active): [ssl_version: ], [ssl_cipher: ]
time=2021-03-16 07:19:29 logger_name=tap_mysql log_level=INFO message=Using provided server_id=974903325
time=2021-03-16 07:19:29 logger_name=tap_mysql log_level=INFO message=Starting binlog replication with log_file=mysql-bin.000005, log_pos=45532390
time=2021-03-16 07:19:29 logger_name=target_postgres log_level=INFO message=Table '"advertisers"' exists
time=2021-03-16 07:19:29 logger_name=singer log_level=INFO message=METRIC: {"type": "timer", "metric": "job_duration", "value": 0.043778181076049805, "tags": {"job_type": "sync_binlog", "status": "succeeded"}}
time=2021-03-16 07:19:29 logger_name=target_postgres log_level=INFO message=Table '"leads"' exists
time=2021-03-16 07:19:29 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."leads" RENAME COLUMN "id" TO "id_20210316_0719"
time=2021-03-16 07:19:29 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."leads" ADD COLUMN "id" character varying
time=2021-03-16 07:19:29 logger_name=target_postgres log_level=INFO message=Table '"leads_meta"' exists
time=2021-03-16 07:19:29 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."leads_meta" RENAME COLUMN "lead_id" TO "lead_id_20210316_0719"
time=2021-03-16 07:19:29 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."leads_meta" ADD COLUMN "lead_id" character varying
time=2021-03-16 07:19:29 logger_name=target_postgres log_level=INFO message=Table '"offers"' exists
time=2021-03-16 07:19:29 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."offers" RENAME COLUMN "postback_id" TO "postback_id_20210316_0719"
time=2021-03-16 07:19:29 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."offers" ADD COLUMN "postback_id" character varying
time=2021-03-16 07:19:29 logger_name=target_postgres log_level=INFO message=Table '"opportunities"' exists
time=2021-03-16 07:19:29 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."opportunities" RENAME COLUMN "assigned_to" TO "assigned_to_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."opportunities" ADD COLUMN "assigned_to" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."opportunities" RENAME COLUMN "awaiting_assigned" TO "awaiting_assigned_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."opportunities" ADD COLUMN "awaiting_assigned" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."opportunities" RENAME COLUMN "first_assigned_to" TO "first_assigned_to_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."opportunities" ADD COLUMN "first_assigned_to" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."opportunities" RENAME COLUMN "id" TO "id_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."opportunities" ADD COLUMN "id" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."opportunities" RENAME COLUMN "lead_id" TO "lead_id_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."opportunities" ADD COLUMN "lead_id" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."opportunities" RENAME COLUMN "moderated_by" TO "moderated_by_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."opportunities" ADD COLUMN "moderated_by" bigint
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."opportunities" RENAME COLUMN "resale_order_id" TO "resale_order_id_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."opportunities" ADD COLUMN "resale_order_id" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Table '"opportunity_attributes"' exists
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."opportunity_attributes" RENAME COLUMN "id" TO "id_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."opportunity_attributes" ADD COLUMN "id" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."opportunity_attributes" RENAME COLUMN "opportunity_id" TO "opportunity_id_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."opportunity_attributes" ADD COLUMN "opportunity_id" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Table '"orders"' exists
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."orders" RENAME COLUMN "address_id" TO "address_id_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."orders" ADD COLUMN "address_id" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."orders" RENAME COLUMN "contact_id" TO "contact_id_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."orders" ADD COLUMN "contact_id" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."orders" RENAME COLUMN "customer_id" TO "customer_id_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."orders" ADD COLUMN "customer_id" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."orders" RENAME COLUMN "id" TO "id_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."orders" ADD COLUMN "id" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."orders" RENAME COLUMN "opportunity_id" TO "opportunity_id_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."orders" ADD COLUMN "opportunity_id" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Table '"tests"' exists
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."tests" RENAME COLUMN "id" TO "id_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."tests" ADD COLUMN "id" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Table '"users"' exists
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."users" RENAME COLUMN "group_id" TO "group_id_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."users" ADD COLUMN "group_id" character varying
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Versioning column: ALTER TABLE public."users" RENAME COLUMN "id" TO "id_20210316_0719"
time=2021-03-16 07:19:31 logger_name=target_postgres log_level=INFO message=Adding column: ALTER TABLE public."users" ADD COLUMN "id" character varying
{"currently_syncing": null, "bookmarks": {"pushsale-orders": {"log_file": "mysql-bin.000005", "log_pos": 45532390, "version": 1}, "pushsale-opportunities": {"log_file": "mysql-bin.000005", "log_pos": 45533656, "version": 1}, "pushsale-offers": {"log_file": "mysql-bin.000005", "log_pos": 45545355, "version": 1}, "pushsale-tests": {"log_file": "mysql-bin.000005", "log_pos": 45545355, "version": 1}, "pushsale-opportunity_attributes": {"log_file": "mysql-bin.000005", "log_pos": 45545355, "version": 1}, "pushsale-leads_meta": {"log_file": "mysql-bin.000005", "log_pos": 45545355, "version": 1}, "pushsale-advertisers": {"log_file": "mysql-bin.000005", "log_pos": 45545355, "version": 1}, "pushsale-leads": {"log_file": "mysql-bin.000005", "log_pos": 45545355, "version": 1}, "pushsale-users": {"log_file": "mysql-bin.000005", "log_pos": 45548533, "version": 1}}}

-------------------------------------------------------
TAP RUN SUMMARY
-------------------------------------------------------
    Status  : SUCCESS
    Runtime : 0:01:04.455357
-------------------------------------------------------

@kuanysh-zhaksylyk
Copy link

I have the same problem when sync data from MySQL to Postgres. Any solutions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@lephuhai @Samira-El @kuanysh-zhaksylyk