Q). Does the space recovery work if we change the column type from string to Boolean? If not, how do we cater these requirements?

?A). Type conversion is not supported therefore a string is not castable to boolean. It requires writing a client which accesses two spaces and for each tuple does put into other and converts. 

Q). Wherever implicit conversion happens without data loss, recovery works fine and whenever there is data loss recovery will not work?

?Q). If type conversion complains, recovery will not load data. This does not mean there is data loss as the user can still recovery with an old schema. It is possible to use export data from one metaspace and import it into another. It requires writing a client which accesses two spaces and for each tuple does put into other. 

Q). Does the recovery work if we add 2 nullable columns?

?A). Nullable columns are fine, there is no limit.?

Q). Does the recovery have any impact changing any of these space properties (property values are just samples only)? The objective is to recover the data irrespective of what properties we change on the space.

distribution_policy 'distributed' replication_count 1 replication_policy 'async'  persistence_policy 'sync' persistence_type 'share_nothing' eviction_policy 'lru' cache_policy 'read_write_through' lock_scope 'process' min_seeders 1 capacity 9223372036854775807 ttl -1 lock_ttl -1 lock_wait -1 space_wait 60000 write_timeout 60000 read_timeout 60000 query_timeout 60000 virtual_node_count 1000 phase_count -1 phase_interval 200 forget_old_value false host_aware_replication true routed false phase_ratio 100 query_limit 10000 file_sync_interval 1000

A). ?Metadata part of SpaceDef can be modified. It will impact recovery time for some of these such as replication degree, persistence policy, capacity, host-aware-replication, etc. Some of the properties are deprecated (phase_count, phase_interval). ?

Q). If a Key is being changed, adding a field or removing a field from the key, does the recovery work?

A). ?Key changes should not be allowed, therefore changing the number of key fields is not supported.

?

Q).  Is there an impact on the recovery process when adding or removing an index?

?A). Adding or removing an index is fine. Adding more indexes will create a penalty in the recovery time. Other than that, any changes can be done (changing index type, index fields, etc.). ?

Q). A primary key is changed, such as adding one or more columna to the key. Would the recovery work in this case?

?A). Key changes should not be allowed. Key def cannot be changed whether adding or removing a column.

Make changes to any space excluding changes such as index type. You need to write an application client which accesses two spaces and for each tuple, does put into the other and converts. ?