[annotations] Fixing migration for annotation layers #4187
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR resolves an issue with the annotation layer migration which @graceguo-supercat noticed during testing where the
value
field should actually be the layer ID. This also provides a one-to-one mapping between upgrade and downgrade, and thus for completeness I added a downgrade method.I tested this locally on a toy slice containing a single annotation layer, confirming that the corresponding record was correct after running
superset db upgrade
andsuperset db downgrade
.Note given there's a downgrade method the check to inspect the type of the layer in the slice is no longer necessary. This was needed if someone previously ran,
to: @fabianmenges @graceguo-supercat @michellethomas
cc: @mistercrunch