Resolution:
Description:
===========
Behavior of metaspace recovery using Shared Nothing Persistence when metaspace structure has been changed.

Environment:
===========
TIBCO ActiveSpaces 2.0.x/2.x
All Operating Systems

Resolution:
========
If you modify the type of a property then the recovery will fail. This is expected behaviour.

If you remove a field the recovery from that space (file) will fail. This is expected behaviour.

If you add a new "nullable" property there is no impact on recovery.

Note:
ActiveSpaces versions 2.0.2 and above allows you to alter the fields in a space that is already defined by using the as-admin utility or by calling Metaspace.alterspace(). The C API and the .NET API provide equivalent operations. There is no disruption in service when you alter the space. Any new fields that you add must be nullable.

Options to migrate after modify or remove a property are (Version 2.0.1 and earlier):

1). Convert existing data from one metaspace to another by reading the stored data  one by one and storing it in the new one.

2). Export the data into CSV files and import back in AS with new updated settings.

Behavior of metaspace recovery using Shared Nothing Persistence when metaspace structure has been changed.