[
https://issues.apache.org/jira/browse/THRIFT-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624906#action_12624906
]
David Reiss commented on THRIFT-122:
------------------------------------
As I said on the other issue, I'm not convinced this is the right way to go. I
would recommend creating a union-like structure that can contain all of the
types you want in your collection. Other possibilities that were discussed in
a previous thread are adding explicit support for unions or a generic variant
type that would allow (nearly) arbitrary combinations of base types and
collections (but not structures). Either of these proposals would (IMO) cover
the heterogeneous collection use case, and neither would require any changes to
existing protocol implementations (they would be serialized as structures and
only have different in-memory behavior).
> 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.
