Docker Installer - Release Notes - 2.18
2.18.2-funcrel
Note
No change in comparison to 2.18.1-funcrel. An equivalent Docker Installer accompanies every release of CAST Imaging. This installer will automatically pull the current release Docker images in both fresh install and upgrade scenarios.
2.18.1-funcrel
Note
No change in comparison to 2.18.0-funcrel. An equivalent Docker Installer accompanies every release of CAST Imaging. This installer will automatically pull the current release Docker images in both fresh install and upgrade scenarios.
2.18.0-funcrel
Note
A structural change has been implemented in this release of CAST Imaging to the Neo4j database in which the CAST Imaging data is stored, primarily to improve performance. This change requires that any existing data in the Neo4j database (i.e. applications imported in previous releases) is migrated to ensure that it matches the new storage structure. This migration process is applied automatically when running an in-place upgrade to this release of CAST Imaging (whether using a traditional Microsoft Windows install or an installation on Docker (Microsoft Windows or Linux) and you do not need to do anything, however, if you have uninstalled a previous release of CAST Imaging and retained the existing data to use with this release (or any future release of CAST Imaging) you must manually run the data storage migration process following the installation of the new release of CAST Imaging to ensure the existing data is correctly migrated. You can find more details about this here: https://doc.castsoftware.com/display/IMAGING/CAST+Imaging+installation+using+existing+data.
Other Updates
| Internal Id | Details |
|---|---|
| IMAGSYS-11590 | Removed unnecessary migration process on installation. |
2.18.0-beta2
Note
A structural change has been implemented in this release of CAST Imaging to the Neo4j database in which the CAST Imaging data is stored, primarily to improve performance. This change requires that any existing data in the Neo4j database (i.e. applications imported in previous releases) is migrated to ensure that it matches the new storage structure. This migration process is applied automatically when running an in-place upgrade to this release of CAST Imaging (whether using a traditional Microsoft Windows install or an installation on Docker (Microsoft Windows or Linux) and you do not need to do anything, however, if you have uninstalled a previous release of CAST Imaging and retained the existing data to use with this release (or any future release of CAST Imaging) you must manually run the data storage migration process following the installation of the new release of CAST Imaging to ensure the existing data is correctly migrated. You can find more details about this here: https://doc.castsoftware.com/display/IMAGING/CAST+Imaging+installation+using+existing+data.
2.18.0-beta1
Note
No change in comparison to 2.18.0-alpha2. An equivalent Docker Installer accompanies every release of CAST Imaging. This installer will automatically pull the current release Docker images in both fresh install and upgrade scenarios.
2.18.0-alpha2
Note
No change in comparison to 2.18.0-alpha1. An equivalent Docker Installer accompanies every release of CAST Imaging. This installer will automatically pull the current release Docker images in both fresh install and upgrade scenarios.
2.18.0-alpha1
Note
No change in comparison to 2.17.1-funcrel. An equivalent Docker Installer accompanies every release of CAST Imaging. This installer will automatically pull the current release Docker images in both fresh install and upgrade scenarios.
Other Updates
| Internal Id | Details |
|---|---|
| IMAGSYS-10118 | Increase number of job threads used by neo4j database |
AJS.$('[data-macro-name="markdown-from-url"] code').each(function(i, block) { hljs.highlightBlock(block); });``AJS.$('[data-macro-name="markdown-from-url"] .language-mermaid').each(function(i, block) { const config = { startOnLoad:true, theme: 'default', flowchart:{ useMaxWidth:false, htmlLabels:true } }; mermaid.initialize(config); window.mermaid.init(undefined, block); });