[connectors] Make names non-nullable#7067
Closed
john-bodley wants to merge 1 commit into
Closed
Conversation
Codecov Report
@@ Coverage Diff @@
## master #7067 +/- ##
=========================================
+ Coverage 64.48% 64.5% +0.02%
=========================================
Files 421 421
Lines 20547 20559 +12
Branches 2250 2250
=========================================
+ Hits 13249 13261 +12
Misses 7171 7171
Partials 127 127
Continue to review full report at Codecov.
|
Member
|
Outside of typos LGTM |
3250807 to
3d2e7e5
Compare
Member
Author
|
@mistercrunch apologies for the copy-and-paste typos. I realized that the |
Member
|
Sweet, well at least the typo made us discover that it wasn't necessary :) LGTM |
0056033 to
1c9ba3d
Compare
38ba9da to
2555b03
Compare
2555b03 to
940519a
Compare
940519a to
452b216
Compare
452b216 to
b581b49
Compare
Member
Author
|
Closing this in favor of resurrecting (and augmenting) the following PRs:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 ensures that the various database values cannot be NULL which surfaced as a result #5445 where it became apparent there could be ill-defined and/or erroneous database values. This is also reflected in the CRUD views which is handled automatically by Flask-AppBuilder. Specifically the following additional fields are now non-NULL:
Druid
datasource_namecolumn_namemetric_name,jsonSQLAlchemy
table_namecolumn_namename,expressionThe attached screenshot provides an example of a form comprising of a required field (*) and form validation upon saving.
Note this PR also includes a migration to update the schema to include the non-nullable fields. In order for this to happen however erroneous records need to be removed and ill-defined records need to be mutated.
Erroneous records are defined when:
Ill-defined records are defined when:
Given that the CRUD model is broken with NULL values the migration mutates the relevant fields to contain the
migration_40f150716b13_prefix. This allows the admin to then provide a cleanup pass if required to remove or update the violating records.to: @graceguo-supercat @michellethomas @mistercrunch @xtinec