Am 12.12.2012 um 17:27 schrieb Erik Fäßler <[email protected]>: > I experimented with CASCompleteSerializer which of course does not offer this > flexibility (but I still wanted to see like it works). Now I was hoping, when > I used CASSerializer, I would perhaps get the flexibility I want.
The CASSerializer can only be used if the CAS metadata remains exactly the same. If you do not change the type system often, you could consider doing - deserialize using the CASCompleteSerializer - serialize as XMI - deserialize XMI into a CAS with the new type system - serialize using the CASCompleteSerializer Afaik another downside of the binary serialization is that even annotations that have been removed from the indexes (deleted) are persisted. These would also get dropped as part of the XMI detour. Cheers, -- Richard -- ------------------------------------------------------------------- Richard Eckart de Castilho Technical Lead Ubiquitous Knowledge Processing Lab (UKP-TUD) FB 20 Computer Science Department Technische Universität Darmstadt Hochschulstr. 10, D-64289 Darmstadt, Germany phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117 [email protected] www.ukp.tu-darmstadt.de Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de -------------------------------------------------------------------
