Include unmapped targets with most queries #27
Conversation
rustybee42
force-pushed
the
rb/unmapped-targets
branch
from
d31ad32 to
3fc3976
Compare
rustybee42
force-pushed
the
rb/unmapped-targets
branch
from
3fc3976 to
bd51015
Compare
rustybee42
force-pushed
the
rb/unmapped-targets
branch
from
bd51015 to
c05d764
Compare
rustybee42
force-pushed
the
rb/unmapped-targets
branch
from
c05d764 to
fd19273
Compare
There was a problem hiding this comment.
suggestion(blocking): it is unfortunate a DB migration is required for this change. So we can at least eliminate the upgrade pain for users (most who are unaffected by this particular change), what do you think about automatically applying minor DB schema updates when needed?
We could introduce a new option for this (e.g., --upgrade=auto) so it is opt in. This would be particularly helpful for environments that use tools like Ansible for automated deployments/upgrades to avoid requiring post-upgrade steps for specific minor releases.
Blocking not because we need to introduce any automatic migration in this PR, but because I want to discuss how we want to generally handle database upgrades in minor releases before we merge our first DB schema update.
Related to #21
Merge together with ThinkParQ/beegfs-go#249 or ctl will crash if there are unmapped targets.