shaoyu-li commented on PR #12364:
URL: https://github.com/apache/gravitino/pull/12364#issuecomment-5211025874
Thank you for your response. You're right that upgrade-1.3.0-to-2.0.0 needs
the same change.
We're running 1.3.0 internally, so a 1.3.0 user needs a way to pick this up
without waiting for 2.0.0. I'd like to add a 1.3.1 schema for that. I'll write
all these scripts:
upgrade-1.3.0-to-1.3.1 the index renames and the table_version_info
primary key
upgrade-1.3.0-to-2.0.0 the same two changes, added to what is already
there, so the direct 1.3.0 -> 2.0.0 path stays equivalent to a fresh 2.0.0
install
upgrade-1.3.1-to-2.0.0 the current 1.3.0 -> 2.0.0 content without the
renames, since 1.3.1 already has them
schema-1.3.1-mysql.sql
Only MySQL is affected, so for h2 and postgresql the 1.3.1 schema is a copy
of 1.3.0 and only the 1.3.1 -> 2.0.0 script is added.
I'll push these to this PR shortly, and open a cherry-pick PR against
branch-1.3 once this one lands. Let me know if you'd rather structure the
version chain differently. Thank you!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
