Difference between revisions of "Archivematica 1.9.1 and Storage Service 0.14.1 release notes"
Jump to navigation
Jump to search
(→Fixed) |
|||
| Line 1: | Line 1: | ||
| − | [[Main_Page|Home]] > [[Release_Notes|Release Notes]] > | + | [[Main_Page|Home]] > [[Release_Notes|Release Notes]] > Archivematica 1.9.1 and Storage Service 0.14.1 release notes |
| − | '''April | + | '''Release date: April 9, 2019''' |
| + | |||
| + | For more information about Archivematica 1.9.x, please see the release notes for [[Archivematica_1.9_and_Storage_Service_0.14_release_notes|Archivematica 1.9.0]]. | ||
| + | |||
| + | ==Upgrading== | ||
| + | |||
| + | If you are upgrading from 1.9.0 to 1.9.1, please ensure that you run the following command: | ||
| + | |||
| + | <code>curl -XPUT 'http://localhost:9200/aips,aipfiles,transfers,transferfiles/_settings' -H "Content-Type: application/json" -d '{"index.mapping.total_fields.limit": 10000, "index.mapping.depth.limit": 1000 }'</code> | ||
| + | |||
| + | This is not required for upgrading from 1.8.x to 1.9.1. | ||
| + | |||
| + | For more information on upgrading, see [https://www.archivematica.org/en/docs/archivematica-1.9/admin-manual/installation-setup/upgrading/upgrading/#upgrade Upgrading Archivematica] in the documentation. | ||
==Fixed== | ==Fixed== | ||
| − | + | * Error in rebuilding elasticsearch AIP index: [https://github.com/archivematica/Issues/issues/595 Issue 595] | |
| − | |||
| − | * Error in rebuilding elasticsearch AIP index: [https://github.com/archivematica/Issues/issues/595 Issue 595 | ||
* AIP index error: ''Limit of total fields [1000] in index [aips] has been exceeded'': [https://github.com/archivematica/Issues/issues/608 Issue 608] | * AIP index error: ''Limit of total fields [1000] in index [aips] has been exceeded'': [https://github.com/archivematica/Issues/issues/608 Issue 608] | ||
* Cannot approve DSpace file-only transfers: [https://github.com/archivematica/Issues/issues/468 Issue 468] | * Cannot approve DSpace file-only transfers: [https://github.com/archivematica/Issues/issues/468 Issue 468] | ||
* Can't build Docker files: [https://github.com/archivematica/Issues/issues/617 Issue 617] | * Can't build Docker files: [https://github.com/archivematica/Issues/issues/617 Issue 617] | ||
* Pointer files are not being saved when Storage Service is on a different VM: [https://github.com/archivematica/Issues/issues/599 Issue 599] | * Pointer files are not being saved when Storage Service is on a different VM: [https://github.com/archivematica/Issues/issues/599 Issue 599] | ||
| − | * indexAIP task fails when using S3 aipstore: [https://github.com/archivematica/Issues/issues/559 Issue 559]. '''Note''' | + | * indexAIP task fails when using S3 aipstore: [https://github.com/archivematica/Issues/issues/559 Issue 559]. |
| + | ** '''Note''': this issue was also found to occur when the Storage Service and dashboard were deployed on different VMs. The fix addresses both situations. | ||
Revision as of 14:33, 9 April 2019
Home > Release Notes > Archivematica 1.9.1 and Storage Service 0.14.1 release notes
Release date: April 9, 2019
For more information about Archivematica 1.9.x, please see the release notes for Archivematica 1.9.0.
Upgrading
If you are upgrading from 1.9.0 to 1.9.1, please ensure that you run the following command:
curl -XPUT 'http://localhost:9200/aips,aipfiles,transfers,transferfiles/_settings' -H "Content-Type: application/json" -d '{"index.mapping.total_fields.limit": 10000, "index.mapping.depth.limit": 1000 }'
This is not required for upgrading from 1.8.x to 1.9.1.
For more information on upgrading, see Upgrading Archivematica in the documentation.
Fixed
- Error in rebuilding elasticsearch AIP index: Issue 595
- AIP index error: Limit of total fields [1000] in index [aips] has been exceeded: Issue 608
- Cannot approve DSpace file-only transfers: Issue 468
- Can't build Docker files: Issue 617
- Pointer files are not being saved when Storage Service is on a different VM: Issue 599
- indexAIP task fails when using S3 aipstore: Issue 559.
- Note: this issue was also found to occur when the Storage Service and dashboard were deployed on different VMs. The fix addresses both situations.