You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2018/10/19 19:54:00 UTC

[jira] [Assigned] (TINKERPOP-2071) gremlin-python: the graphson deserializer for g:Set should return a python set

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

stephen mallette reassigned TINKERPOP-2071:
-------------------------------------------

             Assignee: stephen mallette
    Affects Version/s: 3.3.3
        Fix Version/s:     (was: 3.3.4)

> gremlin-python: the graphson deserializer for g:Set should return a python set
> ------------------------------------------------------------------------------
>
>                 Key: TINKERPOP-2071
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2071
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: python
>    Affects Versions: 3.3.3
>            Reporter: Alan Boudreault
>            Assignee: stephen mallette
>            Priority: Major
>
> This is something that has already been discussed. The reason that a g:Set is deserialized to a list is because Java can return some numerical values that are not differentiate by python. See TINKERPOP-1844 for more details.
> However, I think this is is not something very common so I would like to propose another behavior:
> 1. By default, always return a python set as normal for g:Set
> 2. When we detect the case described, log a warning and return a python list.
> 3. Document properly the limitation and the behavior of g:Set.
> Already discussed with Stephen and we think it's an acceptable behavior. I will provide a PR shortly.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)