[
https://issues.apache.org/jira/browse/DRILL-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013258#comment-16013258
]
ASF GitHub Bot commented on DRILL-5517:
---------------------------------------
GitHub user paul-rogers opened a pull request:
https://github.com/apache/drill/pull/840
DRILL-5517: Size-aware set methods in value vectors
Please see DRILL-5517 for an explanation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/paul-rogers/drill DRILL-5517
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/840.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 #840
----
commit 6d9d8f5e93c7ad0fd45242a3aba43334c9385239
Author: Paul Rogers <prog...@maprtech.com>
Date: 2017-05-16T20:20:32Z
DRILL-5517: Size-aware set methods in value vectors
Please see DRILL-5517 for an explanation.
----
> Provide size-aware set operations in value vectors
> --------------------------------------------------
>
> Key: DRILL-5517
> URL: https://issues.apache.org/jira/browse/DRILL-5517
> Project: Apache Drill
> Issue Type: Improvement
> Affects Versions: 1.11.0
> Reporter: Paul Rogers
> Assignee: Paul Rogers
> Fix For: 1.11.0
>
>
> DRILL-5211 describes a memory fragmentation issue in Drill. The resolution is
> to limit vector sizes to 16 MB (the size of Netty memory allocation "slabs.")
> Effort starts by providing "size-aware" set operations in value vectors which:
> * Operate as {{setSafe()}} while vectors are below 16 MB.
> * Throw a new, specific exception ({{VectorOverflowException}}) if setting
> the value (and growing the vector) would exceed the vector limit.
> The methods in value vectors then become the foundation on which we can
> construct size-aware record batch "writers."
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
