[
https://issues.apache.org/jira/browse/TINKERPOP3-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette closed TINKERPOP3-656.
---------------------------------------
Resolution: Implemented
Assignee: stephen mallette
Fix Version/s: 3.1.0-incubating
Implemented this issue with a simple change to the Builder so that each call to
{{addRegistry}} adds to a list of them to be used in construction of the mapper.
> IoRegistry Chaining
> -------------------
>
> Key: TINKERPOP3-656
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-656
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: io
> Affects Versions: 3.0.0-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Fix For: 3.0.1-incubating, 3.1.0-incubating
>
>
> {{IoRegistry}} is used by vendors to apply custom serializers to {{IO}}
> instances. In some cases, a user may wish to use multiple vendor
> {{IoRegistry}} implementations (e.g. in the case of a data migration from
> Titan to OrientDB you would use both vendor implementations at the same
> time). To do that {{IoRegistry}} should be chainable in some way either by:
> 1. allowing multiple assignments of an {{IoRegistry}} to an {{Mapper.Builder}}
> 2. construction of a {{ChainableIoRegistry}} implementation of {{IoRegistry}}
> that takes multiple {{IoRegistry}} instances and somehow combines them.
> Not sure which is a better approach at this time...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
