[
https://issues.apache.org/jira/browse/HBASE-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005288#comment-13005288
]
ryan rawson commented on HBASE-3117:
------------------------------------
we are on thrift 0.5.0 for trunk, there is a 'libthrift' in the apache repo.
We want to get away from using a people.apache.org repo, so I'd like to see
thrift 0.6.0 get into apache repo before we upgrade.
I hear thrift 0.6.0 has good things for C++ client libraries, but our use of
thrift 0.5.0 on the server side should not prevent clients from using any
version of thrift they wish. What other advantages of thrift 0.6.0 would we get
on the server side?
> Update Thrift to a current version
> ----------------------------------
>
> Key: HBASE-3117
> URL: https://issues.apache.org/jira/browse/HBASE-3117
> Project: HBase
> Issue Type: Improvement
> Components: thrift
> Reporter: Lars Francke
> Assignee: Lars Francke
> Priority: Minor
> Attachments: HBASE-3117.2.patch, HBASE-3117.3.patch.zip,
> thrift-0.5.0.jar
>
>
> Thrift 0.5 has been released already and we want to upgrade to at least 0.3
> but 0.5 has a lot of improvements so that would be the best.
> Unfortunately the Java lib has changed so that we'll have to regenerate the
> current Thrift interface and fix the implementation (byte[] -> ByteBuffer).
> They also have problems getting Thrift into a Maven repository so we'll need
> to do our current workaround again unfortunately and upload it to a
> repository. That would be Ryan's I think?
> I'll upload an updated thrift jar and a patch for the old Thrift code.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
