Is your feature request related to a problem? Please describe.
#655 (feast 0.5.0) introduced several changes in the DB schema. Some are easier to handle (new columns) but some are harder, for instance the PK of feature_sets changed datatypes from VARCHAR to a BIGINT.
Describe the solution you'd like
As a first approach, could we have a manual DB upgrade script linked, per release, in the changelog? It would make life easier for operators, as we wouldn't need to check multiple issues for DB changes.
I think having something like Flyway integrated into the project, as suggested by @ches, would really help in making this process as painless as possible.
Describe alternatives you've considered
Additional context
Is your feature request related to a problem? Please describe.
#655 (feast 0.5.0) introduced several changes in the DB schema. Some are easier to handle (new columns) but some are harder, for instance the PK of
feature_setschanged datatypes from VARCHAR to a BIGINT.Describe the solution you'd like
As a first approach, could we have a manual DB upgrade script linked, per release, in the changelog? It would make life easier for operators, as we wouldn't need to check multiple issues for DB changes.
I think having something like Flyway integrated into the project, as suggested by @ches, would really help in making this process as painless as possible.
Describe alternatives you've considered
Additional context