[ 
https://issues.apache.org/jira/browse/THRIFT-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18023684#comment-18023684
 ] 

Christopher Tubbs commented on THRIFT-5895:
-------------------------------------------

Is this work really in scope of the Thrift project? I understand that it could 
be useful, but this is really tooling to help move away from Thrift's 
services/functionality. It seems more suitable in a separate project.

Adding it to the Thrift project risks making the code less likely to be 
maintained in the future. The developers here are Thrift developers, not 
protobuf or gRPC developers. To ask that this project's developers do the work 
to maintain support for this seems unreasonable to me.

I think this is out of scope, and would suggest hosting this suggested feature 
elsewhere. I think it could be useful, but I don't think it belongs here.

> Proposal: Add a generator to convert Thrift IDL to Protocol Buffers file
> ------------------------------------------------------------------------
>
>                 Key: THRIFT-5895
>                 URL: https://issues.apache.org/jira/browse/THRIFT-5895
>             Project: Thrift
>          Issue Type: New Feature
>          Components: C++ - Compiler
>    Affects Versions: 0.22.0
>            Reporter: Yu Miura
>            Priority: Major
>             Fix For: 0.23.0
>
>
> I would like to propose adding a Thrift → Protobuf generator to Apache 
> Thrift. The generator would take .thrift IDL as input and produce equivalent 
> .proto files, enabling teams to interoperate with Protobuf-based ecosystems 
> while continuing to author schemas in Thrift.
> I plan to submit an initial draft PR for early feedback. Before opening the 
> PR, I wanted to validate interest and design scope with maintainers.
>  
> I would appreciate your feedback. Thank you.
>  
> compare: 
> https://github.com/apache/thrift/compare/master...YuMuuu:thrift:feature/support-grpc



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to