Github user jorgebay commented on the issue:
https://github.com/apache/tinkerpop/pull/842
Sorry I'm late to the party, I haven't got much time during the past weeks:
nice contribution @danielcweber !
I'm a little concerned about the difference between serializers and
deserializers supported.
Can we limit the scope of this PR to types for which we support
serialization and deserialization?
Some of the extended types are not very popular but once we add support for
them, the user base for those could grow. From the user perspective, retrieving
and storing are expected to be symmetric: if one operation is supported the
other should also be.
Mapping 1 type (like `DateTime`) to multiple TinkerPop types could lead to
obscure serialization errors that the user might not be able to identify.
---
