generate-table-partitions is helpful in scaling row validations by breaking up large row validations into smaller chunks. Smaller chunks can be validated without running out of memory. Smaller chunks can also be validated in parallel speeding up row validations. Generate-table-partitions does not support custom query row validations. The problem is that the existing logic uses the tables and primary keys to generate where clauses to partition the table.
There are two options:
require the user to provide a -tbls argument so that generate table partitions can generate the where clauses based on the underlying tables. This may not work in all cases since the underlying tables may have fewer or additional rows than in the custom query.
partition the custom query itself - that is, make the custom query a subquery - extract the primary key(s) and generate the where clauses to partition the custom query.
Hi,
generate-table-partitions is helpful in scaling row validations by breaking up large row validations into smaller chunks. Smaller chunks can be validated without running out of memory. Smaller chunks can also be validated in parallel speeding up row validations. Generate-table-partitions does not support custom query row validations. The problem is that the existing logic uses the tables and primary keys to generate where clauses to partition the table.
There are two options:
Sundar Mudupalli