this naming convention update. • Category [Area of Vitess Subject e.g. VReplication, VTgate, …) • Label for [BugFix, Feature, Enhancement] • Short and descriptive summary • End with corresponding ticket/story compatibility – OLAP – System – VReplication – VTtablet – VTorc – PITR – Examples – Docs – Build – Other • Label – BugFix – Feature – Enhancement – Backport • Title: Short informative summary of the pull request More detailed explanatory text describing the PR for the reviewer Suggested Format: [Category ] [Label] Description #[Ticket_ID] Example: [VTGate] [BugFix] - Fix where clause in information schema with

might wish to benchmark it before merging it. The latter can be done by setting the Benchmark me label to your pull request. Each night, at midnight central european time, the head commit of your pull following sections. • Pull Request Naming • Branch Naming • Commit Message Naming • Tag Naming • Label Addition Feature The most problematic area we see is the Pull Request Naming Convention and Labels vschema: { "sharded": false, "tables": { } } Labels Two class of labels have been created and 1 label from each class must be added to all the pull requests. The two classes and the corresponding labels

this naming convention update. • Category [Area of Vitess Subject e.g. VReplication, VTgate, …) • Label for [BugFix, Feature, Enhancement] • Short and descriptive summary • End with corresponding ticket/story compatibility – OLAP – System – VReplication – VTtablet – VTorc – PITR – Examples – Docs – Build – Other • Label – BugFix – Feature – Enhancement – Backport • Title: Short informative summary of the pull request More detailed explanatory text describing the PR for the reviewer Suggested Format: [Category ] [Label] Description #[Ticket_ID] Example: [VTGate] [BugFix] - Fix where clause in information schema with

might wish to benchmark it before merging it. The latter can be done by setting the Benchmark me label to your pull request. Each night, at midnight central european time, the head commit of your pull following sections. • Pull Request Naming • Branch Naming • Commit Message Naming • Tag Naming • Label Addition Feature The most problematic area we see is the Pull Request Naming Convention and Labels vschema: { "sharded": false, "tables": { } } Labels Two class of labels have been created and 1 label from each class must be added to all the pull requests. The two classes and the corresponding labels

delete a row from the owner table, Vitess will not perform cascading deletes. This is mainly for efficiency reasons; The application is likely capable of doing this more efficiently. 66 As for a lookup

delete a row from the owner table, Vitess will not perform cascading deletes. This is mainly for efficiency reasons; The application is likely capable of doing this more efficiently. Functional Vindexes

delete a row from the owner table, Vitess will not perform cascading deletes. This is mainly for efficiency reasons; The application is likely capable of doing this more efficiently. As for a lookup, you

delete a row from the owner table, Vitess will not perform cascading deletes. This is mainly for efficiency reasons; the application is likely capable of doing this more efficiently. 89 As for a lookup