[
https://issues.apache.org/jira/browse/THRIFT-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623968#action_12623968
]
Chad Walters commented on THRIFT-110:
-------------------------------------
bq. This can decide on whether thrift is usable or not for us.
If non-homogenous collections are make-or-break for you, then let's figure out
what the full requirements and see whether its doable or not. I'm open to
adding support for this as long as we can support it in C++ as well and as long
as it is added in a way that doesn't impact the efficiency of the current
homogeneous collections.
bq. I know what the types are and the types are the ones which are already
defined in the IDL
Are you suggesting that the non-homogeneous collections would only contain base
types? If so, that is a big simplification. If not, that is where things get a
little challenging I think...
> A more compact format
> ----------------------
>
> Key: THRIFT-110
> URL: https://issues.apache.org/jira/browse/THRIFT-110
> Project: Thrift
> Issue Type: Improvement
> Reporter: Noble Paul
>
> Thrift is not very compact in writing out data as (say protobuf) . It does
> not have the concept of variable length integers and various other
> optimizations possible . In Solr we use a lot of such optimizations to make a
> very compact payload. Thrift has a lot common with that format.
> It is all done in a single class
> http://svn.apache.org/viewvc/lucene/solr/trunk/src/java/org/apache/solr/common/util/NamedListCodec.java?revision=685640&view=markup
> The other optimizations include writing type/value in same byte, very fast
> writes of Strings, externalizable strings etc
> We could use a thrift format for non-java clients and I would like to see it
> as compact as the current java version
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
