<
From version < 3.1 >
edited by Thomas Mortagne
on 2012/03/12
To version < 4.1 >
edited by Denis Gervalle
on 2012/03/12
>
Change comment: Note on migration procedure

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ThomasMortagne
1 +XWiki.dgervalle
Content
... ... @@ -8,12 +8,12 @@
8 8  
9 9  == Extension Manager improvements ==
10 10  
11 -=== Extension Manager
11 +=== Extension Manager ===
12 12  
13 13  * Added possibility to choose on which wiki to install an extension
14 14  * When installing/uninstalling extension or any other background job, the result of the job executing is stored on the filesystem so that it can be reviewed later. There is no UI to access it yet but it's always possible to access the saved file on filesystem directly.
15 15  
16 -=== XWiki Repository
16 +=== XWiki Repository ===
17 17  
18 18  * Added a button to update an imported extension
19 19  * It's now possible to extend an Extension sheet with custom informations. For example http://extensions.xwiki.org adds "Bundled with" and "Compatibility" fields.
... ... @@ -34,7 +34,7 @@
34 34  
35 35  == Component related improvements ==
36 36  
37 -=== Role moved from Class to Type ==
37 +=== Role moved from Class to Type ===
38 38  
39 39  In order to support parameterized role like DocumentReferenceResolver<String>, all the APIs of ComponentManager and Component descriptors has been changed to take Type instead of Class. All the old API are still here and working but deprecated.
40 40  
... ... @@ -128,12 +128,32 @@
128 128  
129 129  = Backward Compatibility and Migration Notes =
130 130  
131 -== General Notes ==
131 +== Migration of database IDs ==
132 132  
133 +You need to enable database migration (//xwiki.store.migration=1//) to upgrade existing databases to the new identifier format.
134 +
135 +{{info}}
136 +This is a major migration affecting almost all rows and relations in the database. I may takes a while before the wiki respond to your initial request when you are migrating a large database. The initial request may even timeout but the database migration continue in the background.
137 +{{/info}}
138 +
133 133  {{warning}}
134 -If you're running in a multiwiki setup you'll also need to define the property //xwiki.store.migration.databases=all// to your //xwiki.cfg// file or explicitly name all databases to be migrated as in //xwiki.store.migration.databases=db1,db2,...//.
140 +Avoid to interrupt the database migration process and check the current progress of the database migration in the console output or the log file. The progress may be slow, so be patient during document id and object id conversion.
135 135  {{/warning}}
136 136  
143 +In case of interruption, the migration procedure could be restarted by restarting XWiki, and it will start over where it have been interrupted.
144 +
145 +{{warning}}
146 +We have taken many precaution to provide a reliable migration procedure, but due to the large changes it made, and this release being an unstable one, you should be really careful and ensure that you keep an appropriate backup until you are sure that your data has been properly migrated.
147 +{{/warning}}
148 +
149 +If you have custom mapped classes used externally, be aware that all internal identifier are now full 64bits longs.
150 +
151 +== General Notes ==
152 +
153 +{{info}}
154 +If you're running in a multiwiki setup you'll also need to define the property //xwiki.store.migration.databases// in your //xwiki.cfg// file if you want to explicitly name some databases to be migrated as the default is now to migrate all databases. Database that are not migrated could not be accessed.
155 +{{/info}}
156 +
137 137  You may also want to [[import the default wiki XAR>>Main.Download]] in order to benefit from all the improvements listed above.
138 138  
139 139  {{warning}}
... ... @@ -146,5 +146,4 @@
146 146  
147 147  {{todo/}}
148 148  
149 -{{code language="none"}}
150 -{{/code}}
169 +{{code language="none"}}{{/code}}

Get Connected