Drop backwards-compatibility support for "outlier" (#10903)

Before Synapse 1.31 (#9411), we relied on `outlier` being stored in the
`internal_metadata` column. We can now assume nobody will roll back their
deployment that far and drop the legacy support.
This commit is contained in:
Richard van der Hoff 2021-09-28 15:25:36 +01:00 committed by GitHub
parent 2622b28c5c
commit 8aaa4b7b5d
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 4 additions and 25 deletions

View file

@ -12,9 +12,7 @@
# See the License for the specific language governing permissions and
# limitations under the License.
# When updating these values, please leave a short summary of the changes below.
SCHEMA_VERSION = 64
SCHEMA_VERSION = 64 # remember to update the list below when updating
"""Represents the expectations made by the codebase about the database schema
This should be incremented whenever the codebase changes its requirements on the
@ -46,7 +44,7 @@ Changes in SCHEMA_VERSION = 64:
"""
SCHEMA_COMPAT_VERSION = 59
SCHEMA_COMPAT_VERSION = 60 # 60: "outlier" not in internal_metadata.
"""Limit on how far the synapse codebase can be rolled back without breaking db compat
This value is stored in the database, and checked on startup. If the value in the