From 8ab41c83a8fdd258d8bc98bd0aaf1f5cea864677 Mon Sep 17 00:00:00 2001 From: Matt Riedemann Date: Tue, 8 Aug 2017 14:58:14 -0400 Subject: [PATCH] doc: code review considerations for online data migrations Online data migrations that move something from the cell database to the API database typically create new things in the API DB and on a query, look in the API DB first and then fallback to the cell database. We started supporting multiple cells in Pike, so any online data migrations that move things to the API DB after that will need to be multi-cell aware for the fallback lookup code. This just adds a reminder in the code review guide. Change-Id: If0d7d9b80e336b696aaf87ec13ac18daa1068357 --- doc/source/contributor/code-review.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/source/contributor/code-review.rst b/doc/source/contributor/code-review.rst index 8a8ba5149530..b95534fbdc53 100644 --- a/doc/source/contributor/code-review.rst +++ b/doc/source/contributor/code-review.rst @@ -86,6 +86,9 @@ Database Schema online. Generally, this can and should be hidden within the object layer so that an object can load from either the old or new location, and save to the new one. +* Multiple Cells v2 cells are supported started in the Pike release. + As such, any online data migrations that move data from a cell + database to the API database must be multi-cell aware. REST API =========