[
https://issues.apache.org/jira/browse/DRILL-7733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271822#comment-17271822
]
ASF GitHub Bot commented on DRILL-7733:
---------------------------------------
paul-rogers commented on pull request #2149:
URL: https://github.com/apache/drill/pull/2149#issuecomment-767191625
@vvysotskyi, thanks much for the review. I've made the requested changes. It
appeared the builds for the prior version failed for reasons related to the
environment; perhaps someone wants to take a look.
I would suggest that someone try out the fixes with something that makes
heavy use of the JSON REST API. While I've done simple functional testing, it
would be good to get additional experience with a wider range of use cases.
----------------------------------------------------------------
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
> Use streaming for REST JSON queries
> -----------------------------------
>
> Key: DRILL-7733
> URL: https://issues.apache.org/jira/browse/DRILL-7733
> Project: Apache Drill
> Issue Type: Improvement
> Affects Versions: 1.17.0
> Reporter: Paul Rogers
> Assignee: Paul Rogers
> Priority: Major
> Fix For: 1.19.0
>
>
> Several uses on the user and dev mail lists have complained about the memory
> overhead when running a REST JSON query: {{http:://node:8047/query.json}}.
> The current implementation buffers the entire result set in memory, then lets
> Jersey/Jetty convert the results to JSON. The result is very heavy heap use
> for larger query result sets.
> This ticket requests a change to use streaming. As each batch arrives at the
> Screen operator, convert that batch to JSON and directly stream the results
> to the client network connection, much as is done for the native client
> connection.
> For backward compatibility, the form of the JSON must be the same as the
> current API.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
