chibenwa edited a comment on pull request #464:
URL: https://github.com/apache/james-project/pull/464#issuecomment-856499755
> However, usually when we want to add changes to tables, instead of
introducing breaking changes, don't we recreate the table in a new version?
This is the strategy we adopted so far however:
- it generate too much tables and table are expensive with Cassandra
- generating double the message reads during the migration would be a major
performance hit
For this specific case I think `ALTER TABLE` is simpler and safer.
> I wouldn't be too surprised of people in the community breaking their db
because they didn't read or read too quickly the upgrade notes...
Query preparation would prevent James to start. Nothing to be worried of.
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
