You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@james.apache.org by GitBox <gi...@apache.org> on 2021/05/05 03:21:33 UTC
[GitHub] [james-project] chibenwa opened a new pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
chibenwa opened a new pull request #417:
URL: https://github.com/apache/james-project/pull/417
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] Arsnael commented on pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
Arsnael commented on pull request #417:
URL: https://github.com/apache/james-project/pull/417#issuecomment-836136561
I think @rouazana point makes sense TBH
If for example a user is using 3.3.0 and wants to upgrade later to 3.7.0 (after we release it), he needs to understand that he probably has to upgrade first to 3.6.0 and do all the migration steps up to that version, before jumping on 3.7.0.
If the user jumps directly from 3.3.0 to 3.7.0, James will not start because his Cassandra version is inferior, and he might not understand without proper documentation what he should do to solve it.
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] rouazana commented on pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
rouazana commented on pull request #417:
URL: https://github.com/apache/james-project/pull/417#issuecomment-834388101
> It makes sense to have it per server. Eg JPA do not have the same upgrade path than Distributed...
Right.
> Also I do not understand the meaning of the versions in the cells.
The list of version you need to install to migration from A to B.
Here to migration from 3.3.0 to 3.8.0 you need to install 3.7.0 and 3.8.0. Maybe specifying the last version is useless.
You can also take inspiration from here for example: https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html if it is more clear for 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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] chibenwa edited a comment on pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
chibenwa edited a comment on pull request #417:
URL: https://github.com/apache/james-project/pull/417#issuecomment-834459426
> The list of version you need to install to migration from A to B.
Do we really have to maintain that for all choices of A and B? The cardinality would be pretty high, no? With just `3.6.0`, `3.5.0`, `3.4.0`, `3.3.0`, 3.2.0`, `3.1.0`, `3.0`, upcoming `3.7.0` that is ~32 upgrade paths to maintain (O(n2)).
> You can also take inspiration from here for example: https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html if it is more clear for you.
Ok, thank you finaly!
Yes, I can do that, but I would only maintain such a thing for the distributed server. In `/docs`.
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] chibenwa commented on a change in pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
chibenwa commented on a change in pull request #417:
URL: https://github.com/apache/james-project/pull/417#discussion_r629044177
##########
File path: upgrade-instructions.md
##########
@@ -14,6 +14,23 @@ Note: this section is in progress. It will be updated during all the development
Changes to apply between 3.5.x and 3.6.x will be reported here.
+Change list:
+
+ - [Drop Cassandra schema version prior version 8](#drop-cassandra-schema-version-prior-version-8)
+
+### Drop Cassandra schema version prior version 8
+
+Date 05/05/2021
+
+JIRA: https://issues.apache.org/jira/browse/JAMES-3578
+
+Concerned products: Distributed James, Cassandra-guice James server
+
+In an effort to simplify the code base, we dropped support for Cassandra schema version prior version 8.
+
+Installation running older schema version than version 5 needs to rely on releases 3.6.x to upgrade to schema version 8,
+before upgrading to an eventual newer version.
Review comment:
I did not wanted to mention unreleased stuff in the Antora documentation just yet.
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] chibenwa merged pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
chibenwa merged pull request #417:
URL: https://github.com/apache/james-project/pull/417
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] chibenwa commented on pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
chibenwa commented on pull request #417:
URL: https://github.com/apache/james-project/pull/417#issuecomment-833627839
Hello Raphael.
I don't understand what you ask for. We already document the upgrade path in the upgrade instructions.
What is ambiguous in the existing doc?
Aren't people upgrading from say 3.4.0 read all the upgrade instrctions between their version and the target one?
Can we be more clear here?
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] rouazana commented on pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
rouazana commented on pull request #417:
URL: https://github.com/apache/james-project/pull/417#issuecomment-833658339
Let's take an example. I want to migrate from 3.3.0 to 3.8.0.
For that, I need to read upgrade notes, but I probably need to only install 3.6.0 and 3.8.0.
Before this change, I would have need only to install 3.8.0. Is it clearer?
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] chibenwa commented on pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
chibenwa commented on pull request #417:
URL: https://github.com/apache/james-project/pull/417#issuecomment-833672997
I got the feeling the upgrade notes already contain that information.
What form would you give it then?
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] Arsnael commented on a change in pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
Arsnael commented on a change in pull request #417:
URL: https://github.com/apache/james-project/pull/417#discussion_r629035446
##########
File path: docs/modules/servers/pages/distributed/operate/index.adoc
##########
@@ -24,4 +24,38 @@ distributed James operators.
We also included a guide for xref:distributed/operate/migrating.adoc[migrating existing data] into the distributed server.
-Read more about xref:distributed/operate/cassandra-migration.adoc[Cassandra data migration].
\ No newline at end of file
+Read more about xref:distributed/operate/cassandra-migration.adoc[Cassandra data migration].
+
+== Upgrading
+
+This section sum up and links upgrade instructions for people willing to upgrade their Distributed server to newer versions.
Review comment:
```suggestion
This section sums up and links upgrade instructions for people willing to upgrade their Distributed server to newer versions.
```
##########
File path: docs/modules/servers/pages/distributed/operate/cassandra-migration.adoc
##########
@@ -17,13 +17,8 @@ Note that currently the progress can be tracked by logs.
Here are the implemented migrations:
-* *From V5 to V6* : Goal is to no longer rely on an UDT partition key for mailboxPath tables. Entries will be migrated
-to mailboxPathV2 table relying on a composite primary key.
-* *From V6 to V7* : Goal is to populate mapping_sources projection table. This table allows finding the source of a given redirection, which is
-handy for things like mail aliases (I want to list aliases rewritting things to bob). Without this projection table being available,
-(ie we rely on schema version 6 or less) such information is obtained through a full table scan, unoptimized. From schema version 7,
-the optimized projection can safely be used.
-* *From V7 to V8* : Add UID_VALIDITY to mailboxPath table in order not to mandate mailbox table reads.
Review comment:
Hmmm did we ever test versioning in our antora doc yet? That could be a good candidate to start :)
##########
File path: docs/modules/servers/pages/distributed/operate/index.adoc
##########
@@ -24,4 +24,38 @@ distributed James operators.
We also included a guide for xref:distributed/operate/migrating.adoc[migrating existing data] into the distributed server.
-Read more about xref:distributed/operate/cassandra-migration.adoc[Cassandra data migration].
\ No newline at end of file
+Read more about xref:distributed/operate/cassandra-migration.adoc[Cassandra data migration].
+
+== Upgrading
+
+This section sum up and links upgrade instructions for people willing to upgrade their Distributed server to newer versions.
+
+.dnsservice.xml content
Review comment:
That's your table description? dnsservice.xml?
##########
File path: upgrade-instructions.md
##########
@@ -14,6 +14,23 @@ Note: this section is in progress. It will be updated during all the development
Changes to apply between 3.5.x and 3.6.x will be reported here.
+Change list:
+
+ - [Drop Cassandra schema version prior version 8](#drop-cassandra-schema-version-prior-version-8)
+
+### Drop Cassandra schema version prior version 8
+
+Date 05/05/2021
+
+JIRA: https://issues.apache.org/jira/browse/JAMES-3578
+
+Concerned products: Distributed James, Cassandra-guice James server
+
+In an effort to simplify the code base, we dropped support for Cassandra schema version prior version 8.
+
+Installation running older schema version than version 5 needs to rely on releases 3.6.x to upgrade to schema version 8,
+before upgrading to an eventual newer version.
Review comment:
ah actually you mention it here :) But I guess we need to mention it in the Antora doc too, probably safer...
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] chibenwa commented on pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
chibenwa commented on pull request #417:
URL: https://github.com/apache/james-project/pull/417#issuecomment-833986197
Ok, let's do that array in another PR.
Because I have several remarks:
- It makes sense to have it per server. Eg JPA do not have the same upgrade path than Distributed...
- Also I do not understand the meaning of the versions in the cells.
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] rouazana commented on pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
rouazana commented on pull request #417:
URL: https://github.com/apache/james-project/pull/417#issuecomment-833487857
I ask it also here: can we have some documentation to reference the migration path. I mean how to get from any old version to the last version.
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] chibenwa commented on pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
chibenwa commented on pull request #417:
URL: https://github.com/apache/james-project/pull/417#issuecomment-834459426
> The list of version you need to install to migration from A to B.
Do we really have to maintain that for all choices of A and B? The cardinality would be pretty high, no? With just `3.6.0`, `3.5.0`, `3.4.0`, `3.3.0`, 3.2.0`, `3.1.0`, `3.0`, upcoming `3.7.0` that is ~32 upgrade paths to maintain (O(n2)).
> You can also take inspiration from here for example: https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html if it is more clear for you.
Ok, thank you finnaly!
Yes, I can do that, but I would only maintain such a thing for the distributed server. In `/docs`.
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] chibenwa commented on a change in pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
chibenwa commented on a change in pull request #417:
URL: https://github.com/apache/james-project/pull/417#discussion_r629043873
##########
File path: docs/modules/servers/pages/distributed/operate/cassandra-migration.adoc
##########
@@ -17,13 +17,8 @@ Note that currently the progress can be tracked by logs.
Here are the implemented migrations:
-* *From V5 to V6* : Goal is to no longer rely on an UDT partition key for mailboxPath tables. Entries will be migrated
-to mailboxPathV2 table relying on a composite primary key.
-* *From V6 to V7* : Goal is to populate mapping_sources projection table. This table allows finding the source of a given redirection, which is
-handy for things like mail aliases (I want to list aliases rewritting things to bob). Without this projection table being available,
-(ie we rely on schema version 6 or less) such information is obtained through a full table scan, unoptimized. From schema version 7,
-the optimized projection can safely be used.
-* *From V7 to V8* : Add UID_VALIDITY to mailboxPath table in order not to mandate mailbox table reads.
Review comment:
:+1: but we only have the 3.6.0 tag yet
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] chibenwa commented on pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
chibenwa commented on pull request #417:
URL: https://github.com/apache/james-project/pull/417#issuecomment-840386408
@rouazana @Arsnael satisfied by the last version of the doc?
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] chibenwa commented on a change in pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
chibenwa commented on a change in pull request #417:
URL: https://github.com/apache/james-project/pull/417#discussion_r629057218
##########
File path: docs/modules/servers/pages/distributed/operate/cassandra-migration.adoc
##########
@@ -17,13 +17,8 @@ Note that currently the progress can be tracked by logs.
Here are the implemented migrations:
-* *From V5 to V6* : Goal is to no longer rely on an UDT partition key for mailboxPath tables. Entries will be migrated
-to mailboxPathV2 table relying on a composite primary key.
-* *From V6 to V7* : Goal is to populate mapping_sources projection table. This table allows finding the source of a given redirection, which is
-handy for things like mail aliases (I want to list aliases rewritting things to bob). Without this projection table being available,
-(ie we rely on schema version 6 or less) such information is obtained through a full table scan, unoptimized. From schema version 7,
-the optimized projection can safely be used.
-* *From V7 to V8* : Add UID_VALIDITY to mailboxPath table in order not to mandate mailbox table reads.
Review comment:
Yes.
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] rouazana commented on a change in pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
rouazana commented on a change in pull request #417:
URL: https://github.com/apache/james-project/pull/417#discussion_r633442799
##########
File path: docs/modules/servers/pages/distributed/operate/index.adoc
##########
@@ -24,4 +24,47 @@ distributed James operators.
We also included a guide for xref:distributed/operate/migrating.adoc[migrating existing data] into the distributed server.
-Read more about xref:distributed/operate/cassandra-migration.adoc[Cassandra data migration].
\ No newline at end of file
+Read more about xref:distributed/operate/cassandra-migration.adoc[Cassandra data migration].
+
+== Upgrading
+
+This section sums up and links upgrade instructions for people willing to upgrade their Distributed server to newer versions.
+
+.Upgrade path
+|===
+| Upgrade from | Recommended upgrade path to 3.7.0 (unreleased)
+
+| 3.6.0
+| Rolling upgrade to 3.7.0 (unreleased). No specific upgrade instructions to perform.
+
+| 3.5.0
+| 1. Upgrade, and apply link:https://github.com/apache/james-project/blob/master/upgrade-instructions.md#360-version[3.6.0 upgrade instructions]
+
+Note: Because of ElasticSearch upgrade (6.3 -> 7.10) this migration cannot be done in a rolling fashion manner.
+
+2. Rolling upgrade to 3.7.0 (unreleased). No specific upgrade instructions to perform.
+
+
+| 3.4.0
+| 1. Rolling upgrade to 3.5.0, and apply link:https://github.com/apache/james-project/blob/master/upgrade-instructions.md#350-version[3.6.0 upgrade instructions]
Review comment:
```suggestion
| 1. Rolling upgrade to 3.5.0, and apply link:https://github.com/apache/james-project/blob/master/upgrade-instructions.md#350-version[3.5.0 upgrade instructions]
```
##########
File path: docs/modules/servers/pages/distributed/operate/index.adoc
##########
@@ -24,4 +24,47 @@ distributed James operators.
We also included a guide for xref:distributed/operate/migrating.adoc[migrating existing data] into the distributed server.
-Read more about xref:distributed/operate/cassandra-migration.adoc[Cassandra data migration].
\ No newline at end of file
+Read more about xref:distributed/operate/cassandra-migration.adoc[Cassandra data migration].
+
+== Upgrading
+
+This section sums up and links upgrade instructions for people willing to upgrade their Distributed server to newer versions.
+
+.Upgrade path
+|===
+| Upgrade from | Recommended upgrade path to 3.7.0 (unreleased)
+
+| 3.6.0
+| Rolling upgrade to 3.7.0 (unreleased). No specific upgrade instructions to perform.
+
+| 3.5.0
+| 1. Upgrade, and apply link:https://github.com/apache/james-project/blob/master/upgrade-instructions.md#360-version[3.6.0 upgrade instructions]
+
+Note: Because of ElasticSearch upgrade (6.3 -> 7.10) this migration cannot be done in a rolling fashion manner.
+
+2. Rolling upgrade to 3.7.0 (unreleased). No specific upgrade instructions to perform.
+
+
+| 3.4.0
+| 1. Rolling upgrade to 3.5.0, and apply link:https://github.com/apache/james-project/blob/master/upgrade-instructions.md#350-version[3.6.0 upgrade instructions]
+
+2. Upgrade to 3.6.0, and apply link:https://github.com/apache/james-project/blob/master/upgrade-instructions.md#360-version[3.5.0 upgrade instructions]
Review comment:
```suggestion
2. Upgrade to 3.6.0, and apply link:https://github.com/apache/james-project/blob/master/upgrade-instructions.md#360-version[3.6.0 upgrade instructions]
```
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] chibenwa commented on a change in pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
chibenwa commented on a change in pull request #417:
URL: https://github.com/apache/james-project/pull/417#discussion_r629043959
##########
File path: docs/modules/servers/pages/distributed/operate/index.adoc
##########
@@ -24,4 +24,38 @@ distributed James operators.
We also included a guide for xref:distributed/operate/migrating.adoc[migrating existing data] into the distributed server.
-Read more about xref:distributed/operate/cassandra-migration.adoc[Cassandra data migration].
\ No newline at end of file
+Read more about xref:distributed/operate/cassandra-migration.adoc[Cassandra data migration].
+
+== Upgrading
+
+This section sum up and links upgrade instructions for people willing to upgrade their Distributed server to newer versions.
+
+.dnsservice.xml content
Review comment:
```suggestion
.Upgrade path
```
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] rouazana commented on a change in pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
rouazana commented on a change in pull request #417:
URL: https://github.com/apache/james-project/pull/417#discussion_r633442799
##########
File path: docs/modules/servers/pages/distributed/operate/index.adoc
##########
@@ -24,4 +24,47 @@ distributed James operators.
We also included a guide for xref:distributed/operate/migrating.adoc[migrating existing data] into the distributed server.
-Read more about xref:distributed/operate/cassandra-migration.adoc[Cassandra data migration].
\ No newline at end of file
+Read more about xref:distributed/operate/cassandra-migration.adoc[Cassandra data migration].
+
+== Upgrading
+
+This section sums up and links upgrade instructions for people willing to upgrade their Distributed server to newer versions.
+
+.Upgrade path
+|===
+| Upgrade from | Recommended upgrade path to 3.7.0 (unreleased)
+
+| 3.6.0
+| Rolling upgrade to 3.7.0 (unreleased). No specific upgrade instructions to perform.
+
+| 3.5.0
+| 1. Upgrade, and apply link:https://github.com/apache/james-project/blob/master/upgrade-instructions.md#360-version[3.6.0 upgrade instructions]
+
+Note: Because of ElasticSearch upgrade (6.3 -> 7.10) this migration cannot be done in a rolling fashion manner.
+
+2. Rolling upgrade to 3.7.0 (unreleased). No specific upgrade instructions to perform.
+
+
+| 3.4.0
+| 1. Rolling upgrade to 3.5.0, and apply link:https://github.com/apache/james-project/blob/master/upgrade-instructions.md#350-version[3.6.0 upgrade instructions]
Review comment:
```suggestion
| 1. Rolling upgrade to 3.5.0, and apply link:https://github.com/apache/james-project/blob/master/upgrade-instructions.md#350-version[3.5.0 upgrade instructions]
```
##########
File path: docs/modules/servers/pages/distributed/operate/index.adoc
##########
@@ -24,4 +24,47 @@ distributed James operators.
We also included a guide for xref:distributed/operate/migrating.adoc[migrating existing data] into the distributed server.
-Read more about xref:distributed/operate/cassandra-migration.adoc[Cassandra data migration].
\ No newline at end of file
+Read more about xref:distributed/operate/cassandra-migration.adoc[Cassandra data migration].
+
+== Upgrading
+
+This section sums up and links upgrade instructions for people willing to upgrade their Distributed server to newer versions.
+
+.Upgrade path
+|===
+| Upgrade from | Recommended upgrade path to 3.7.0 (unreleased)
+
+| 3.6.0
+| Rolling upgrade to 3.7.0 (unreleased). No specific upgrade instructions to perform.
+
+| 3.5.0
+| 1. Upgrade, and apply link:https://github.com/apache/james-project/blob/master/upgrade-instructions.md#360-version[3.6.0 upgrade instructions]
+
+Note: Because of ElasticSearch upgrade (6.3 -> 7.10) this migration cannot be done in a rolling fashion manner.
+
+2. Rolling upgrade to 3.7.0 (unreleased). No specific upgrade instructions to perform.
+
+
+| 3.4.0
+| 1. Rolling upgrade to 3.5.0, and apply link:https://github.com/apache/james-project/blob/master/upgrade-instructions.md#350-version[3.6.0 upgrade instructions]
+
+2. Upgrade to 3.6.0, and apply link:https://github.com/apache/james-project/blob/master/upgrade-instructions.md#360-version[3.5.0 upgrade instructions]
Review comment:
```suggestion
2. Upgrade to 3.6.0, and apply link:https://github.com/apache/james-project/blob/master/upgrade-instructions.md#360-version[3.6.0 upgrade instructions]
```
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] Arsnael commented on a change in pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
Arsnael commented on a change in pull request #417:
URL: https://github.com/apache/james-project/pull/417#discussion_r629044836
##########
File path: docs/modules/servers/pages/distributed/operate/cassandra-migration.adoc
##########
@@ -17,13 +17,8 @@ Note that currently the progress can be tracked by logs.
Here are the implemented migrations:
-* *From V5 to V6* : Goal is to no longer rely on an UDT partition key for mailboxPath tables. Entries will be migrated
-to mailboxPathV2 table relying on a composite primary key.
-* *From V6 to V7* : Goal is to populate mapping_sources projection table. This table allows finding the source of a given redirection, which is
-handy for things like mail aliases (I want to list aliases rewritting things to bob). Without this projection table being available,
-(ie we rely on schema version 6 or less) such information is obtained through a full table scan, unoptimized. From schema version 7,
-the optimized projection can safely be used.
-* *From V7 to V8* : Add UID_VALIDITY to mailboxPath table in order not to mandate mailbox table reads.
Review comment:
but that change would be for the 3.7.0 right?
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org
[GitHub] [james-project] rouazana commented on pull request #417: JAMES-3578 Drop Cassandra schema support prior version 8
Posted by GitBox <gi...@apache.org>.
rouazana commented on pull request #417:
URL: https://github.com/apache/james-project/pull/417#issuecomment-833677286
Ideally an array
Version to install for migration:
From/To | 3.3.0 | 3.4.0 | 3.5.0 | 3.6.0 | 3.7.0 | 3.8.0
------------|--------|---------|--------|--------|---------|--------
3.3.0 | / | 3.4.0 | 3.5.0 | 3.6.0 | 3.7.0 | 3.7.0,3.8.0
... |
3.8.0| / | / | / | / | / | /
--
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:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org