Skip to content

workload/schemachange: classify and handle errors in all operations #56119

@jayshrivastava

Description

@jayshrivastava

Right now errors occur very frequently inside the schemachange workload and there is no mechanism that checks to see if the error makes sense or not. For example, if we try to add a column to a table that does not exist, we should assert that we receive the right error code for an undefined table.

All ops should be updated up to the standard above:

Once all the ops are up to date:

Metadata

Metadata

Labels

A-testingTesting tools and infrastructureC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions