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 2021/04/09 13:47:00 UTC

[jira] [Closed] (TINKERPOP-2457) Add a max_content_length parameter to DriverRemoteConnection in the Python client

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

Stephen Mallette closed TINKERPOP-2457.
---------------------------------------
    Fix Version/s: 3.4.11
                   3.5.0
         Assignee: Stephen Mallette
       Resolution: Done

> Add a max_content_length parameter to DriverRemoteConnection in the Python client
> ---------------------------------------------------------------------------------
>
>                 Key: TINKERPOP-2457
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2457
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: python
>    Affects Versions: 3.4.8
>            Reporter: Kelvin R. Lawrence
>            Assignee: Stephen Mallette
>            Priority: Major
>             Fix For: 3.5.0, 3.4.11
>
>
> I was recently trying to retrieve a subgraph (basically just the air-routes part of the air-routes data set) using Gremlin Python over Web Sockets. My query kept failing. After some investigation I discovered that the default maximum result set for Tornado is 10*1024*1024 (10 gig)
> The current Python client does not offer a way to override this from an application. I would like to propose that we add a `max_content_length` parameter to the constructor for DriverRemoteConnection so that one could do something like:
> {code:java}
> connection = DriverRemoteConnection(
>                  endpoint,
>                  'g',
>                  max_content_length=1024 ** 3){code}
>  
> I coded up a prototype for this and it seems to work well. I did not investigate if we need to also provide such a setting when connecting via HTTP yet.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)