Hi Luke, I don't think having different serializers for different regions is possible. The issue is that your objects may be serialized in places where there is no associated region, for example passing arguments to a function. You could also potentially copy an object from one region to another. So the serialization of objects is not really tied to a region at all.
-Dan On Mon, Oct 19, 2015 at 6:54 AM, Luke Shannon <[email protected]> wrote: > It looks like a serializer can only be configured per cache: > > http://gemfire.docs.pivotal.io/latest/developing/data_serialization/use_pdx_serializer.html > > I want to have certain regions go through a custom serializer and others > not. > > Right now it looks the options are: > 1. Put logic in the toData and fromData to decide to serialize or not > 2. Utilize the Mapping Pdx Serializer and configure it to work on specific > classes: > http://docs.spring.io/spring-data-gemfire/docs/current/api/org/springframework/data/gemfire/mapping/MappingPdxSerializer.html > > The challenge is there a tons of object types persisting to the cache. It > would be too much logic in step 1 and the config in step 2 would be pretty > messy. > > The ideal solution would be to map a serializer to a Region...is this > possible? >
