Hi,

We use form 6 compressed binaries to persist the CAS. We now want to make a 
change to the type system that is not directly compatible, although in 
principle the new type system is really a subset from a data perspective, so we 
want to migrate existing binaries to the new type system, but we don’t know 
how. The change is as follows:

In the existing type system we have a type A with a FSArray feature of element 
type X, and we want to change X to Y where Y contains a genuine feature subset 
of X. This means we basically want to replace X with Y for the FSArray and 
ditch a few attributes of X when loading the CAS into the new type system.

Had the CAS been stored in JSON this would be trivial by just mapping the 
attributes that they have in common, but when I try to load the CAS binary into 
the new target type system it chokes with an EOF, so I don’t know if that is at 
all possible with a form 6 compressed CAS binary?

I pocked a bit around in the reference, API and mailing list archive but I was 
not able to find anything useful. I can of course keep parallel attributes for 
both X and Y and then have a separate step that makes an explicit 
conversion/copy, but I prefer to avoid this. I would appreciate any input to 
the problem, thanks :)

Cheers,
Mario













Reply via email to