Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

CLONE - pt-archiver shifts the colums

Description

Hello,

We loaded a table via the pt-archiver tool on MySQL env 8.0.18 version and toolkit version 3.2.0.1, command like: /usr/bin/pt-archiver --source h=localhost,u=root,p=***,D=test,t=test,b=1 --dest h=server01,u=root,p=***,D=test,t=test,b=1 --no-check-charset --why-quit --progress 10000 --header --bulk-insert --commit-each --limit 500000 --sleep 1 --statistics --no-delete --where "1=1";

But for some records two columns became one , both columns text type (using json array as well):

`boards` text COMMENT 'The player selections',
`multiplier` text COMMENT 'The wager multiplier'

And CHARSET=utf8mb4 .

On source we have: 

boards: [{"btp":1,"id":1,"mlt":[1],"pnl":[{"qp":false,"req":5,"sel":[1,2,3,4,5]}],"sts":[{"bt":1,"cl":1}]}]

multiplier: [1]

And on target we get:

boards: [{"btp":1,"id":1,"mlt":[1],"pnl":[{"qp":false,"req":5,"sel":[1,2,3,4,5]}],"sts":[{"bt":1,"cl":1}]}] [1]

multiplier: [752973, 752974] – this should be in the next column

Environment

None

Attachments

1
  • 03 Nov 2020, 01:19 PM

Smart Checklist

Activity

Show:

Jira Bot December 25, 2020 at 3:56 PM

Hello ,
It's been 52 days since this issue went into Incomplete and we haven't heard
from you on this.

At this point, our policy is to Close this issue, to keep things from getting
too cluttered. If you have more information about this issue and wish to
reopen it, please reply with a comment containing "jira-bot=reopen".

Jira Bot December 17, 2020 at 2:57 PM

Hello ,
It's jira-bot again. Your bug report is important to us, but we haven't heard
from you since the previous notification. If we don't hear from you on
this in 7 days, the issue will be automatically closed.

Jira Bot December 2, 2020 at 1:57 PM

Hello ,
I'm jira-bot, Percona's automated helper script. Your bug report is important
to us but we've been unable to reproduce it, and asked you for more
information. If we haven't heard from you on this in 3 more weeks, the issue
will be automatically closed.

Lalit Choudhary November 3, 2020 at 2:54 PM

Hi ,

MySQL version should matter here.

Can you test the same on non-prod? here I want to know if this issue consistently reproduciable. 

Αναστασία Παπαχριστοπούλου November 3, 2020 at 1:34 PM

Hello,

Thank you for looking into this. MySQL was 8.018, not sure if it affects the results. And when using --replace instead of bulk insert we did not receive the same behavior.

Incomplete

Details

Assignee

Reporter

Priority

Smart Checklist

Created October 30, 2020 at 2:05 PM
Updated February 29, 2024 at 8:56 PM
Resolved December 25, 2020 at 3:56 PM

Flag notifications