Hawkin
/
arangodb
mirror of https://gitee.com/bigwinds/arangodb
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Upgrade info for queues.

This commit is contained in:
Alan Plum 2015-06-09 13:56:10 +02:00
parent fbf6c0021b
commit 584dfdbb5d
2 changed files with 22 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Documentation/Books/Users/Upgrading/Upgrading26.mdpp
View File

@ -1,11 +1,11 @@
!CHAPTER Upgrading to ArangoDB 2.5
!CHAPTER Upgrading to ArangoDB 2.6
Please read the following sections if you upgrade from a previous version to
ArangoDB 2.5. Please be sure that you have checked the list of [changes in 2.5](../Upgrading/UpgradingChanges25.html)
ArangoDB 2.6. Please be sure that you have checked the list of [changes in 2.6](../Upgrading/UpgradingChanges26.html)
before upgrading.
Please note first that a database directory used with ArangoDB 2.5
cannot be used with earlier versions (e.g. ArangoDB 2.4) any
Please note first that a database directory used with ArangoDB 2.6
cannot be used with earlier versions (e.g. ArangoDB 2.5) any
more. Upgrading a database directory cannot be reverted. Therefore
please make sure to create a full backup of your existing ArangoDB
installation before performing an upgrade.
@ -64,7 +64,7 @@ The last line of the output should look like this:
Please check the full output the `--upgrade` run. Upgrading may produce errors, which need
to be fixed before ArangoDB can be used properly. If no errors are present or
they have been resolved manually, you can start ArangoDB 2.5 regularly.
they have been resolved manually, you can start ArangoDB 2.6 regularly.
!SECTION Upgrading a cluster planned in the web interface

17
Documentation/Books/Users/Upgrading/UpgradingChanges26.mdpp
View File

@ -3,6 +3,23 @@
It is recommended to check the following list of incompatible changes **before**
upgrading to ArangoDB 2.6, and adjust any client programs if necessary.
!SECTION Foxx changes
!SUBSECTION Foxx Queues
Foxx Queue job type definitions were previously based on functions and had to be registered before use. Due to changes in 2.5 this resulted in problems when restarting the server or defining job types incorrectly.
Function-based job types have been deprecated in 2.6 and will be removed entirely in 2.7.
In order to convert existing function-based job types to the new script-based job types, create custom scripts in your Foxx app and reference them by their name and the mount point of the app they are defined in. Official job types from the Foxx app store can be upgraded by upgrading from the 1.x version to the 2.x version of the same app.
In order to upgrade queued jobs to the new job types, you need to update the `type` property of the affected jobs in the database's `_jobs` system collection. In order to see the collection in the web interface you need to enable the collection type "System" in the collection list options.
Example:
Before: `"type": "mailer.postmark"`
After: `"type": {"name": "mailer", "mount": "/my-postmark-mailer"}`
!SECTION Changed behavior