[29/50] incubator-tinkerpop git commit: Update upgrade docs.

[ok...@apache.org]

Update upgrade docs.


Project: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/commit/0defd91a
Tree: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/tree/0defd91a
Diff: http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/diff/0defd91a

Branch: refs/heads/TINKERPOP-1033
Commit: 0defd91a992e1abbbefc1519871f501bc17a4711
Parents: 34db892
Author: Stephen Mallette <sp...@genoprime.com>
Authored: Thu Dec 24 08:30:35 2015 -0500
Committer: Stephen Mallette <sp...@genoprime.com>
Committed: Thu Dec 24 08:30:35 2015 -0500

----------------------------------------------------------------------
 docs/src/upgrade/release-3.1.x-incubating.asciidoc | 15 +++++++++++++++
 1 file changed, 15 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-tinkerpop/blob/0defd91a/docs/src/upgrade/release-3.1.x-incubating.asciidoc
----------------------------------------------------------------------
diff --git a/docs/src/upgrade/release-3.1.x-incubating.asciidoc b/docs/src/upgrade/release-3.1.x-incubating.asciidoc
index b50f3e1..8f487a2 100644
--- a/docs/src/upgrade/release-3.1.x-incubating.asciidoc
+++ b/docs/src/upgrade/release-3.1.x-incubating.asciidoc
@@ -161,6 +161,21 @@ link:https://issues.apache.org/jira/browse/TINKERPOP-1000[TINKERPOP-1000]
 Graph Database Providers
 ^^^^^^^^^^^^^^^^^^^^^^^^
 
+Custom ClassResolver
+++++++++++++++++++++
+
+For providers who have built custom serializers in Gryo, there is a new feature open that can be considered.  A
+`GryoMapper` can now take a custom Kryo `ClassResolver`, which means that custom types can be coerced to other types
+during serialization (e.g. a custom identifier could be serialized as a `HashMap`).  The advantage to taking this
+approach is that users will not need to have the provider's serializers on the client side.  They will only need to
+exist on the server (presuming that the a type is coerced to a type available on the client, of course).  The downside
+is that serialization is then no longer a two way street. For example, a custom `ClassResolver` that coerced a
+custom identifier to `HashMap` would let the client work with the identifier as a `HashMap`, but the client would then
+have to send that identifier back to the server as a `HashMap` where it would be recognized as a `HashMap` (not an
+identifier).
+
+See: link:https://issues.apache.org/jira/browse/TINKERPOP-1064[TINKERPOP-1064]
+
 Feature Consistency
 +++++++++++++++++++