[
https://issues.apache.org/jira/browse/THRIFT-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17840810#comment-17840810
]
Jens Geyer commented on THRIFT-640:
-----------------------------------
[Example of how it works can be found in
optional_required_default.thrift|https://github.com/apache/thrift/blob/master/lib/netstd/Tests/Thrift.PublicInterfaces.Compile.Tests/optional_required_default.thrift]
> Support deprecation
> -------------------
>
> Key: THRIFT-640
> URL: https://issues.apache.org/jira/browse/THRIFT-640
> Project: Thrift
> Issue Type: New Feature
> Components: Java - Compiler
> Reporter: Nathan Marz
> Assignee: Daniel Wolf
> Priority: Minor
> Fix For: 0.10.0
>
> Attachments: thrift-640-java-deprecation.patch
>
>
> Sometimes we do schema migrations and it would be cool to be able to have
> deprecation functionality from Thrift. At the most basic level, we should be
> able to annotate a field as deprecated and have the compiler generate
> "@Deprecated" annotations in the Java code.
> Sometimes though, you may want creators of structs to be forced to use new
> fields, but you still want to be able to read the old fields until you have
> everything migrated over. In this case you could mark a field as
> "strong-deprecated" and just not generate any setters for those fields (only
> getters). This would force all users of the struct to migrate to new schema,
> since the code won't compile otherwise.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
