[
https://issues.apache.org/jira/browse/THRIFT-5340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17270612#comment-17270612
]
Jens Geyer commented on THRIFT-5340:
------------------------------------
RE "useful to document" vs undocumented behaviour: When someone starts to
document undocumented behaviour it becomes a defacto standard. In other words,
people can expect this to be a reliable thing to build upon. But some things
may be deliberately left undocumented to kind of "protect" the internal
implementation. As long as something is undocumented, it is internal and may be
subject to change at any time. If it is documented, it becomes subject to
compatibility issues. This is not always what you want as a developer. There is
a public contract and there is internals. Not everything should be made of the
public contract, for good reasons.
> 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)
