This is an automated email from the ASF dual-hosted git repository.
jorgebg pushed a commit to branch TINKERPOP-2150
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
The following commit(s) were added to refs/heads/TINKERPOP-2150 by this push:
new 325a6c8 TINKERPOP-2150 Changelog and docs
325a6c8 is described below
commit 325a6c8a66f92862d9b5912f13ff63c26bc88c79
Author: Jorge Bay Gondra <jorgebaygon...@gmail.com>
AuthorDate: Wed Feb 6 10:25:30 2019 +0100
TINKERPOP-2150 Changelog and docs
---
CHANGELOG.asciidoc | 1 +
docs/src/reference/gremlin-applications.asciidoc | 1 +
2 files changed, 2 insertions(+)
diff --git a/CHANGELOG.asciidoc b/CHANGELOG.asciidoc
index 1e5b36e..5f54049 100644
--- a/CHANGELOG.asciidoc
+++ b/CHANGELOG.asciidoc
@@ -29,6 +29,7 @@ This release also includes changes from <<release-3-3-6,
3.3.6>>.
* Fixed up `SparqlStrategy` so that it could be used properly with
`RemoteStrategy`.
* Fixed `ByteBuffer` serialization for GraphBinary.
* Added easier to understand exceptions for connection problems in the
Gremlin.Net driver.
+* Support configuring the type registry builder for GraphBinary.
[[release-3-4-0]]
=== TinkerPop 3.4.0 (Release Date: January 2, 2019)
diff --git a/docs/src/reference/gremlin-applications.asciidoc
b/docs/src/reference/gremlin-applications.asciidoc
index 1e41815..e2e0145 100644
--- a/docs/src/reference/gremlin-applications.asciidoc
+++ b/docs/src/reference/gremlin-applications.asciidoc
@@ -1555,6 +1555,7 @@ It has the MIME type of
`application/vnd.graphbinary-v1.0` and the following con
|Key |Description |Default
|custom |A list of classes with custom kryo `Serializer` implementations
related to them in the form of `<class>;<serializer-class>`. |_none_
|ioRegistries |A list of `IoRegistry` implementations to be applied to the
serializer. |_none_
+|builder |Name of the `TypeSerializerRegistry.Builder` instance to be used to
construct the `TypeSerializerRegistry`. |_none_
|=========================================================
As described above, there are multiple ways in which to register serializers
for GraphBinary-based serialization. Note
