[ 
https://issues.apache.org/jira/browse/THRIFT-3896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416594#comment-15416594
 ] 

ASF GitHub Bot commented on THRIFT-3896:
----------------------------------------

GitHub user kdlan opened a pull request:

    https://github.com/apache/thrift/pull/1062

    THRIFT-3896: fix map type with string key can not access deserialized by 
php extension

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kdlan/thrift master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/thrift/pull/1062.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1062
    
----
commit 822adc5bc9cd14f374cc1ad7309c1ee6fc9b5010
Author: 董菲 <[email protected]>
Date:   2016-08-11T05:35:50Z

    THRIFT-3896: fix map type with string key can not access deserialized by 
php extension

----


> map<string,string> data with number string key cannot access that 
> deserialized by php extension
> -----------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-3896
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3896
>             Project: Thrift
>          Issue Type: Bug
>          Components: PHP - Library
>    Affects Versions: 0.9.3
>         Environment: php 5.5.9
>            Reporter: Fei Dong
>         Attachments: test.php
>
>
> Give a key like '2345',  in php script,  
> {noformat}array('2345'=>'value'){noformat}
>  will be processed to 
> {noformat}array(2345=>'value'){noformat}
> The extension now deserialized data {noformat}{'2345':'value'}{noformat} 
> to 
> {noformat}array('2345'=>'value'){noformat}
>  and php code can not access the key by {noformat}$arr['2345']{noformat}.
> Attachment is a simple script that reproduce this situation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to