Migrating the Presto Repository from 3.0 to 3.1

Migration of artifacts or data is not required when upgrading Presto from version 3.0 to version 3.1. There have, however, been minor additions or updates to configuration properties that must be added to or updated in a 3.0 Presto Repository to use that repository for Presto 3.1.

To add or update these properties, you must use the database management tool for the database hosting the Presto Repository to run a set of SQL statements. For HSQL, the default database:

2. Run the manager.bat script for Windows environments or the manager.sh script for Linux, OS X or UNIX environments and log in using an account with privileges to insert records.

UPDATE CONFIGURATION SET CONFIGVALUE = 'false' WHERE CONFIGKEY = 'security.filtersearchresult';

INSERT INTO CONFIGURATION (CONFIGKEY, CONFIGVALUE) VALUES ('security.showOnlyExecutableItems', 'false');

INSERT INTO CONFIGURATION (CONFIGKEY, CONFIGVALUE) VALUES ('snapshot.on', 'false');

UPDATE CONFIGURATION SET CONFIGVALUE = 'serviceURL, Etag, Expires, Last-modified, Cache-Control, Date,Content-Type, Set-Cookie, Content-Disposition' WHERE CONFIGKEY = 'cache.httpheaders.whitelist';

INSERT INTO CONFIGURATION (CONFIGKEY, CONFIGVALUE) VALUES ('http.socket.timeout','0');

INSERT INTO CONFIGURATION (CONFIGKEY, CONFIGVALUE) VALUES ('http.connection.timeout','0');