[
https://issues.apache.org/jira/browse/THRIFT-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624865#action_12624865
]
Noble Paul commented on THRIFT-122:
-----------------------------------
A lot of it is covered in THRIFT-110 but let us cover them once again
Our (Solr) requirements are actually very simple.
Our output is an Object which comprises of collections (lists,maps,primitives)
and one custom type object . So actually we need base types as well as structs
in these collections.
Currently we support a lot of formats xml,json,ruby and a very compact binary
format (works only w/ java) . If thrift has support for heterogeneous
collections then we can consider this as a format for fast data transfer. I am
not aware of our clients using C++ . They are mostly web shops and use
java/php/python/ruby .
> Allow heterogeneous collections
> -------------------------------
>
> Key: THRIFT-122
> URL: https://issues.apache.org/jira/browse/THRIFT-122
> Project: Thrift
> Issue Type: New Feature
> Reporter: Noble Paul
>
> Currently thrift only supports homogeneous collections . But , that is very
> restrictive for many languages which allows heterogeneous collections
> implementation details
> the IDL can allow syntax
> {code}
> list<?>
> set<?>
> map<?,?>
> map<?,the-type>
> map<the-type,?>
> {code}
> While writing down data use a type modifier to say whether key (1), value(2)
> or both(3) are wild cards
> for a List/Set use a type modifier 1 to specify that it is heterogeneous
> If it is a homogeneous collection do it the way it is done now.
> Or else
> add type information just before the data. So it adds an extra byte/element
> For ma
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
