Platform Release 7 Notes
From n² wiki
Nearby: Platform Releases
These are notes on new features and bug fixes that are planned for release 7, released to internal staging on 21st November 2007 and due to go to live on 29th November
[edit] Restoring Snapshots
Store owners can now submit a scheduled job which will replace a store's existing content or metadata with that contained in a snapshot. Any pre-existing snapshot for the store can be used and the restore can be performed by directly specifying the URI of snapshot in the store's snapshot collection. A store can be used as normal while a snapshot is being restored although any changes made during this period will be lost. The restoration process is designed to be robust and any failures will not affect the status of the target store. There is a very short period of unavailability for the store as the content, metadata and indexes are swapped over to the ones contained in the snapshot. In normal operation this period should be less than a second. (Related Jira issues: jira:CAL-369)
[edit] Unavailable Stores
From this release, the platform administrators can set stores to be unavailable. While a store is in the unavailable state, all HTTP interactions will return a 503 Service Unavailable status. Applications should check for this status code when attempting to access a store and take appropriate action such as informing the user. Where possible a Retry-after header is sent by the platform along with the 503 response which could be used by applications to determine whether it is worth attempting the submission after a period of time or to simply fail the request. (Related Jira issues: jira:CAL-370)
[edit] Configuration Security Changes
This release relaxes the security requirements for viewing the configuration of a store. Previously the user required the configure store capability to retrieve configuration such as the field/predicate map or query profile. This has been changed so that users now only need the basic search capability. This places it in the same category as searching the Contentbox or using the Facet Service. Users still require configure store capability to change the configuration for a store. We believe this change will promote reuse of store configuration and also encourage more detailed cross searching of stores. Applications that want to target multiple, arbitrary stores need to know how that store is configured and which fields are available for searching and this change enables that. Stores can make their configuration private by restricting the basic search capability to named users. (Related Jira issues: jira:CAL-512)
