[infinispan-issues] [JBoss JIRA] (ISPN-1409) Introduce a binary-stream upgrading CacheLoader

[Mircea Markus (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720571#comment-12720571 ] 

Mircea Markus commented on ISPN-1409:
-------------------------------------

[~galderz] so this is for upgrading not only the ISPN version but user objects as well? I guess this is not critical for the HR-based upgrades we'll support in 5.2?
                
> Introduce a binary-stream upgrading CacheLoader
> -----------------------------------------------
>
>                 Key: ISPN-1409
>                 URL: https://issues.jboss.org/browse/ISPN-1409
>             Project: Infinispan
>          Issue Type: Feature Request
>            Reporter: Sanne Grinovero
>            Assignee: Manik Surtani
>             Fix For: 6.0.0.Final
>
>
> We need a CacheLoader decorator able to chain sets of two different Externalizers which are targeting the same Java type to transform from one binary format to the next binary format.
> Example: a Person object stored in the cache and an Externalizer is coupled to it. In a new release the Externalizer is changed to provide a different binary representation. Using the old one the stream is transformed from a byte[] to a Person, then this Java instance is feed to the new Externalizer implementation to get the new corresponding byte[]; the updated stream is stored in the decorated CacheLoader so that the nodes going to be attached to the cache store and using the new Externalizer will be fine.
> A little complexity is introduced if the cache has to know about different sets of Externalizers if several different types need to be upgraded. A possible solution is to use a single decorator instance for each type, creating a chain of decorators if they are able to pass "as is" each externalizer id they are not directly coupled to.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira