[
https://issues.apache.org/jira/browse/THRIFT-5340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269573#comment-17269573
]
Jens Geyer commented on THRIFT-5340:
------------------------------------
{code}
I could not find a section in the documentation outlining the schema
evolution/versioning features that Thrift provides.
{code}
That could be because a design idea of Thrift is to support soft versioning. A
schema can evolve as needed and - following a few simple rules - still be held
compatible with earlier versions of that schema.
{code}
I'm talking about the Compact Protocol in particular. I have not ran schema
evolution experiments for other encodings.
{code}
Unfortunately you did not talk about what those experiments could be, but
Thrifts transport/protocol stack is highly modular. So in fact the same
service(s) can be offered by the same server at the same time in a lot of ways.
In that regard, the compact protocol is just one way to do it, and there is
nothing that makes it special in any way. Its just a means to an end, not
different to any of the other protocols.
> Document schema evolution features
> ----------------------------------
>
> Key: THRIFT-5340
> URL: https://issues.apache.org/jira/browse/THRIFT-5340
> Project: Thrift
> Issue Type: Improvement
> Components: Documentation
> Reporter: Juan Cruz Viotti
> Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> I could not find a section in the documentation outlining the schema
> evolution/versioning features that Thrift provides.
> In case there is none, I volunteer to write the first draft, as I've been
> writing a paper involving Apache Thrift as part of my MSc at University of
> Oxford, and ran plenty of schema evolution experiments.
> Please let me know your thoughts and where would this section fit!
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
