-
Notifications
You must be signed in to change notification settings - Fork 130
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
Do not put results_info in the db. #2071
Conversation
afebb4e
to
e5a6a0b
Compare
Rebased! |
Rebased. |
Rendered data does not belong in the db.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good on DEV
PROD updated, thank you @vdbergh |
If I'm not wrong, we can write a script to drop the Jul 04 21:25:39 ns304014 pserve[52240]: The run object 668444967a1863935cee42ba does not validate: run['results_info'] is not in the schema
Jul 04 21:28:45 ns304014 pserve[52240]: Clean_wtt_map: 105 active workers...
Jul 04 21:28:45 ns304014 pserve[52240]: Clean_wtt_map: 106 active workers...
Jul 04 21:28:45 ns304014 pserve[52240]: The run object 6685df348c84573fdb76449d does not validate: run['results_info'] is not in the schema
Jul 04 21:31:49 ns304014 pserve[52240]: Clean_wtt_map: 106 active workers...
Jul 04 21:31:49 ns304014 pserve[52240]: The run object 6684724e7a1863935cee42f9 does not validate: run['results_info'] is not in the schema |
Yes we can. After this PR it will just be ignored, so it would be nice to get rid of it. |
Ok, I will wrote a script to clean the key/value, testing it on DEV. |
Rendered data does not belong in the db.