[ https://issues.apache.org/jira/browse/THRIFT-5340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17269589#comment-17269589 ]
Juan Cruz Viotti commented on THRIFT-5340: ------------------------------------------ Hi [~jensg], > A schema can evolve as needed and - following a few simple rules - still be >held compatible with earlier versions of that schema. Exactly. I was trying to find a list of such simple rules. But I couldn't find them anywhere (maybe I didn't look in the right place?) > 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. For example, I'm creating a schema that defines a list of a scalar type. Then, I transform the schema that has a list of a structure where the scalar is the first and only element. I then encode data with the old schema and attempt to decode it with the new schema, and viceversa, to determine if the schema transformation is forwards, backwards, or fully compatible. > 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)