pt-table-checksum: boundaries as parameters

Registered by Sheeri K. Cabral on 2017-09-22

I would like to be able to use pt-table-checksum such that I can specify the boundaries. For example:

pt-table-checksum --tables foo,bar,baz --index=PRIMARY --lower-boundary=500 --upper-boundary=1000 --replicate....

This would checksum based on the primary key (for example, autoincrement ID), 500 rows in each of the foo, bar, baz tables, from id=500 to id=1000. It would be great to be able to preserve chunking too (so if the span was 5 million rows instead of 500 rows).

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Sheeri K. Cabral
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Can this be already addressed by the --where param?
https://www.percona.com/doc/percona-toolkit/LATEST/pt-table-checksum.html#cmdoption-pt-table-checksum-where

The condition I stated specified the index to use, not the specific field, so I'm not sure how that would work. I could assume the index was named "id" or something. I could test that out. Ideally, though, being able to set the *index* boundaries manually is the desired application.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.