-
Notifications
You must be signed in to change notification settings - Fork 13.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[connectors] Make names non-nullable #7067
[connectors] Make names non-nullable #7067
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.
|
Outside of typos LGTM |
3250807
to
3d2e7e5
Compare
@mistercrunch apologies for the copy-and-paste typos. I realized that the |
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
Closing this in favor of resurrecting (and augmenting) the following PRs:
|
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_name
column_name
metric_name
,json
SQLAlchemy
table_name
column_name
name
,expression
The 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