[
https://issues.apache.org/jira/browse/ARROW-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329296#comment-16329296
]
ASF GitHub Bot commented on ARROW-1712:
---------------------------------------
xhochy commented on a change in pull request #1481: ARROW-1712: [C++] Add
method to BinaryBuilder to reserve space for value data
URL: https://github.com/apache/arrow/pull/1481#discussion_r162157558
##########
File path: cpp/src/arrow/builder.cc
##########
@@ -1222,9 +1222,14 @@ Status BinaryBuilder::Init(int64_t elements) {
Status BinaryBuilder::Resize(int64_t capacity) {
DCHECK_LT(capacity, std::numeric_limits<int32_t>::max());
// one more then requested for offsets
- RETURN_NOT_OK(offsets_builder_.Resize((capacity + 1) * sizeof(int64_t)));
+ RETURN_NOT_OK(offsets_builder_.Resize((capacity + 1) * sizeof(int32_t)));
return ArrayBuilder::Resize(capacity);
}
+
+Status BinaryBuilder::ReserveData(int64_t capacity) {
+ DCHECK_LT(capacity, std::numeric_limits<int32_t>::max());
+ return value_data_builder_.Resize(capacity * sizeof(int64_t));
Review comment:
Why do we multiply here with `int64_t`? I would expect that `ReserveData(x)`
will lead to `value_data_capacity() = x`.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> [C++] Add method to BinaryBuilder to reserve space for value data
> -----------------------------------------------------------------
>
> Key: ARROW-1712
> URL: https://issues.apache.org/jira/browse/ARROW-1712
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++
> Reporter: Wes McKinney
> Assignee: Panchen Xue
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.9.0
>
>
> The {{Resize}} and {{Reserve}} methods only reserve space for the value
> offsets. When building binary/string arrays with a known size (or some
> reasonable estimate), it would be more efficient to reserve once at the
> beginning to prevent internal reallocations
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
