Hi all, Changing the type of column from VARCHAR(80) to VARCHAR(60) would also require a data migration (i.e. a schema migration to add a new column with the "correct" type, changes to the object, data migration logic) as it is not an "online" DDL operation according to [1]. Adding a new API microversion seems to be easier. Thanks, Roman [1] https://dev.mysql.com/doc/refman/5.7/en/innodb-create-index-overview.html#innodb-online-ddl-column-properties On Tue, Jan 17, 2017 at 10:19 AM, Sergey Nikitin <snikitin at mirantis.com> wrote: > Hi, Zhenyu! > > I think we should ask DB guys about migration. But my personal opinion is > that DB migration is much painful than new microversion. > >> But it seems too late to have a microversion for this cycle. > > > Correct me if I'm wrong but I thought that Feature Freeze will be in action > Jan 26. > https://wiki.openstack.org/wiki/Nova/Ocata_Release_Schedule > > Even if we need a new microversion I think it will be a specless > microversion and patch will change about 5 lines of code. We can merge such > patch in one day. > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >