Marko digging into TINKERPOP-1592 (his comments on the "[DISCUSS] Remaining
Items for 3.3.0") has made me basically realize there isn't much value to
doing Gryo 3.0 at this point. More reasoning over on that thread.
On Tue, Jun 27, 2017 at 9:25 AM, Stephen Mallette
wrote:
> We currently have a w
We currently have a wide range of serialization options in Gryo around
different types of "detached" Vertex/Edge instances which typically just
used the default Kryo FieldSerializer. As mentioned earlier in this thread,
I've wanted to change that pattern a bit for Gryo 3.0. I think that we can
have
Now that we have gremlin-io-test for 3.3.0 which tests different versions
of gryo/graphson over different versions of tinkerpop (meaning the current
version you build with ensure that it can still read/write the old formats)
do we need to do this:
https://issues.apache.org/jira/browse/TINKERPOP-13
Just wanted to note that Gryo 3.0 work is happening here in case anyone
wants to follow along:
https://issues.apache.org/jira/browse/TINKERPOP-1698
I have a branch setup. I think I'm going to clean up Gremlin Server
configuration files for 3.3.0 and remove a bunch of the old serializers.
The conf
I'd really like to get our IO situation really solid in 3.3.0 and while we
talk about GraphSON a lot I think Gryo still has an important place in our
serialization story. Gryo covers an extended set of classes that goes
beyond what we cover in GraphSON. I don't know if all those registered
classes
