Difference between revisions of "Archivematica 1.9.1 and Storage Service 0.14.1 release notes"
Jump to navigation
Jump to search
(Created page with "Home > Release Notes > Minor release notes template '''April ##, 2019:''' ==Fixed== List bugfixes with a link to the Github issue. * Bugfix...") |
(→Fixed) |
||
Line 7: | Line 7: | ||
List bugfixes with a link to the Github issue. | List bugfixes with a link to the Github issue. | ||
− | * | + | * 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] |
− | * | + | * 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] | ||
+ | * 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''' that this issue was also found to occur when the Storage Service and pipeline were deployed on different VMs. The fix addresses both situations. |
Revision as of 13:17, 4 April 2019
Home > Release Notes > Minor release notes template
April ##, 2019:
Fixed
List bugfixes with a link to the Github issue.
- 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: 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 that this issue was also found to occur when the Storage Service and pipeline were deployed on different VMs. The fix addresses both situations.