[
https://issues.jboss.org/browse/IPROTO-119?page=com.atlassian.jira.plugin...
]
Nistor Adrian commented on IPROTO-119:
--------------------------------------
This is fixed now, but I have second thoughts about it. Since we do not maintain any state
in the WrappedMessageTypeMapper callback we cannot know if we are invoked by an old client
that needs TypeId translation or not. Also, we need to introduce an option to discard the
TypeId. A possible solution would be to return a negative value from
WrappedMessageTypeMapper.mapTypeId. I also have second thought about
WrappedMessageTypeMapper.mapTypeName. Type names should never change during schema
evolution. We could allow that for more flexibility, but I'd rather remove that and
keep things as simple as possible.
Introduce a customizable TypeId mapper to support changing type ids
(and names) for schema evolution
----------------------------------------------------------------------------------------------------
Key: IPROTO-119
URL:
https://issues.jboss.org/browse/IPROTO-119
Project: Infinispan ProtoStream
Issue Type: Enhancement
Reporter: Nistor Adrian
Assignee: Nistor Adrian
Priority: Major
Fix For: 4.3.0.Alpha13
This should be a simple interface for mapping type ids in and out. Should be specified in
Configuration
--
This message was sent by Atlassian Jira
(v7.13.8#713008)