[
https://issues.apache.org/jira/browse/DRILL-3874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941728#comment-14941728
]
ASF GitHub Bot commented on DRILL-3874:
---------------------------------------
Github user cwestin commented on the pull request:
https://github.com/apache/drill/pull/181#issuecomment-145149090
I just squashed and pushed with the valueCount + 1 for the
BaseRepeatedValueVector, along with using valueCount in getBufferSizeFor()
instead of getAccessor().getValueCount(). I opened
https://issues.apache.org/jira/browse/DRILL-3876 for the proper long term
solution, and https://issues.apache.org/jira/browse/DRILL-3889 for the
getBufferSize()/getBufferSizeFor() improvement. Can one of you please merge
this for 1.2 now?
> flattening large JSON objects consumes too much direct memory
> -------------------------------------------------------------
>
> Key: DRILL-3874
> URL: https://issues.apache.org/jira/browse/DRILL-3874
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Affects Versions: 1.1.0
> Reporter: Chris Westin
> Assignee: Chris Westin
>
> A JSON record has a field whose value is an array with 20,000 elements; the
> record's size is 4MB. A select is used to flatten this. The query profile
> reports that the peak memory utilization was 8GB, most of it used by the
> flatten.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
