Back
Adding new Attributes to Collections does not set default values
When I add a new attribute to an existing collection, all exisiting documents initialize that attribute to null, even though it has a default value set. I added the attr through CLI
TL;DR
Issue: Adding new attributes to collections does not set default values for existing documents causing problems in the production instance.
Solution: Currently, there is no direct solution mentioned in the thread.
Additional note: The issue persists regardless of whether the attribute is added through the command-line interface or the dashboard.Just checked and this issue also does exist when an Attr is added via the dashboard. Present on both localhost 1.7.4 and Cloud which I assume is running 1.8.0
In the meantime, is there a way to update all the docs in a collection so I can do this manually for now? My prod instance is breaking because of this bug
