[
https://issues.apache.org/jira/browse/HAWQ-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215092#comment-15215092
]
ASF GitHub Bot commented on HAWQ-577:
-------------------------------------
GitHub user shivzone opened a pull request:
https://github.com/apache/incubator-hawq/pull/522
HAWQ-577. Updated PXF metadata api to stream response
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/incubator-hawq HAWQ-577
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-hawq/pull/522.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 #522
----
commit 68e30075976aff3e4b79dca08d5033e99c901b07
Author: Shivram Mani <[email protected]>
Date: 2016-03-28T23:31:34Z
HAWQ-577. Updated PXF metadata api to stream response
----
> Stream PXF metadata response
> -----------------------------
>
> Key: HAWQ-577
> URL: https://issues.apache.org/jira/browse/HAWQ-577
> Project: Apache HAWQ
> Issue Type: Bug
> Components: PXF
> Reporter: Shivram Mani
> Assignee: Shivram Mani
>
> getMetadata api returns the metadata corresponding to the user specified
> pattern. There is no limit to the #of tables the pattern can correspond do
> and the current approach of building in memory the json object might not
> scale.
> We needed to serialize them inside a streaming object similar to the approach
> used for streaming the FragmentsResponse
> The same applies also for the debug function that prints metadata of all the
> items - if there are too many of them the StringBuilder will run out of
> memory. The solution in the fragments case was to print a log of one fragment
> at a time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
