[
https://issues.apache.org/jira/browse/THRIFT-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624914#action_12624914
]
Noble Paul commented on THRIFT-122:
-----------------------------------
I am not expecting this to be available in the existing binary protocol. So no
backward compatibility problems must arise (If that is what you are concerned
about) . I can change the issue description
I am willing to wait for the new dense protocol to complete because anyway this
release of Solr will not need it. So next release is what we are aiming for.
bq.As I said on the other issue, I'm not convinced this is the right way to go.
This issue is not specifically for my own project . I may be able to work
around the problems in some way. If you are familiar with programming in
languages like java, C# ,python etc you may know that it is an extremely common
practice to have heterogeneous collections. Having native support for those
use cases is *extremely important* .
> 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.
