The gryo format has seen some change since we first went to GA but all
changes have been done in a backward compatible way such that a file
created with 3.0.0 could be read by all versions up to 3.1.1.  Given what
we've seen of usage, we've accumulated a number of tickets that would
improve gryo's efficiency and fix some problems. You can catch up on what
these tickets are here:

https://issues.apache.org/jira/browse/TINKERPOP-1182
https://issues.apache.org/jira/browse/TINKERPOP-1122
https://issues.apache.org/jira/browse/TINKERPOP-1128

Of course, implementing these tickets would introduce a breaking change if
we were to just implement them in the current version of gryo.  Rather than
introduce a break I think we just need to stamp out a new version of gryo
that will no longer be compatible with the previous version.

It would also be nice to get this ticket in place in the process

https://issues.apache.org/jira/browse/TINKERPOP-1130

which proposes maintaining IO compatibility across versions and validating
that compatibility with tests,

Anyway, I think this is something that might be best done for 3.2.0 even
though it likely shouldn't bring any breaks with it. Any thoughts/concerns?

Reply via email to