[TINKERPOP-656] IoRegistry Chaining

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Implemented
• Affects Version/s: 3.0.0-incubating
• Fix Version/s: 3.0.1-incubating, 3.1.0-incubating
• Component/s: io
• Assignee: Stephen Mallette
• Reporter: Stephen Mallette
• Created: 05/May/15 14:59
• Updated: 28/Jul/15 17:05
• Resolved: 28/Jul/15 17:05

Description

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...