[
https://issues.apache.org/jira/browse/ARROW-3740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702153#comment-16702153
]
Francois Saint-Jacques commented on ARROW-3740:
-----------------------------------------------
Should we just refuse downsizing a non-flushed builder?
> [C++] Calling ArrayBuilder::Resize with length smaller than current appended
> length results in invalid state
> ------------------------------------------------------------------------------------------------------------
>
> Key: ARROW-3740
> URL: https://issues.apache.org/jira/browse/ARROW-3740
> Project: Apache Arrow
> Issue Type: Bug
> Components: C++
> Affects Versions: 0.11.1
> Reporter: Wes McKinney
> Assignee: Francois Saint-Jacques
> Priority: Major
> Fix For: 0.12.0
>
>
> This was brought up by the Go patch ARROW-3613. If you append some data to a
> builder, then call {{Resize}} with something smaller than what's reported by
> {{length()}}, the capacity will be updated, but the length will not. So I
> think further appends would probably segfault. Either way we should add some
> tests for this case of "shrinking" a builder (which destroys data, but it's
> permitted by the API
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
