Excerpt |
---|
Planned release: End of april Released: May 12th 2014 |
Highlights
- Improved Job priority functionality to handle an arbitrary harvester pools. See
Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 81c76265-cab2-3ba5-b74d-ee7cd9a2765e |
---|
key | NAS-2212 |
---|
|
Harvest Channels for details. - The extended field functionality should now be working correctly. See
Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 81c76265-cab2-3ba5-b74d-ee7cd9a2765e |
---|
key | NAS-1725 |
---|
|
Upgrade-notes
DatabaseUpgrade-notes
Upgrading settings
The queuePriority
setting in the harvester.harvesting section has changed to channel. See the harvester deploy configuration description for details. Note that the channel names in the settings needs to correspond to the HarvestDB's harvestchannel table definition.
Database migration
The harvest database need to be updated before starting NetarchiveSuite 4.2 the first time using the HarvestdatabaseUpdateApplication program. Information on how to do that can be found in the additional tools manual under Harvester tools. If you don't do it, the following two applications will not start: GUIApplication and HarvestJobManagerApplication .
Table 'jobs' moves from version: 9 to 10 with the following change:
Table 'harvestdefinitions' moves from version: 3 to 4 with the following change:
Table 'extendedfield' moves from version: 1 to 2 with the following change:
Table 'extendedfieldvalue' moves from version: 1 to 2 with the following change:
Add table 'harvestchannel' in version 1 as
Settings
4. This can be done in the ways:
Automatic
Running the HarvestdatabaseUpdateApplication program will automatically update the DB from a given version to the 4.4 DB.
Manual
Run the relevant update sql directly on the DB: