[ https://issues.apache.org/jira/browse/TINKERPOP-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314019#comment-17314019 ]
ASF GitHub Bot commented on TINKERPOP-2457: ------------------------------------------- spmallette opened a new pull request #1413: URL: https://github.com/apache/tinkerpop/pull/1413 https://issues.apache.org/jira/browse/TINKERPOP-2457 I'm not sure how this will merge to `master` at the moment, or whether that merge is relevant there given the work to move from tornado to aiohttp. I sense this work will merge before that, so we'll see how it becomes relevant or not. Builds with `mvn clean install -pl gremlin-python` VOTE +1 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > 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 > Priority: Major > > 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)