thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James E. King, III (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (THRIFT-3190) In perl, a thrift set<> type should use a more proper native implementation
Date Wed, 01 Feb 2017 12:59:51 GMT

     [ https://issues.apache.org/jira/browse/THRIFT-3190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James E. King, III reassigned THRIFT-3190:
------------------------------------------

    Assignee: James E. King, III

> In perl, a thrift set<> type should use a more proper native implementation
> ---------------------------------------------------------------------------
>
>                 Key: THRIFT-3190
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3190
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Perl - Library
>    Affects Versions: 0.9.2
>            Reporter: James E. King, III
>            Assignee: James E. King, III
>            Priority: Minor
>
> Currently a set<> type in Thrift equates to a hash where the value of each type
is set to 1.  The keys are interpreted as strings and therefore lose their ordering.  The
TestClient for cpp sends:
> The TestServer for perl (which I am writing to verify SSL server refactoring) receives:
> $thing	HASH(0x35da228)={ -1 => '1', -2 => '1', 0 => '1', 1 => '1', 2 =>
'1' }	
> Note how -1 and -2 are transposed.  Further, there are no set manipulations available.
> Recommend the use of Set::Scalar as a required perl dependency for proper set operation.
 This would be a breaking change but necessary to achieve proper set semantics and operations
from the native thrift type.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message