You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/07/03 19:51:00 UTC
[jira] [Commented] (DRILL-5517) Provide size-aware set operations
in value vectors
[ https://issues.apache.org/jira/browse/DRILL-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072859#comment-16072859 ]
ASF GitHub Bot commented on DRILL-5517:
---------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/drill/pull/840
> 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
> Labels: ready-to-commit
> 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.4.14#64029)