[C++] Concatenating a single array is a compaction utility

[bkietz]

Describe the enhancement requested

Concatenation of a single array can be used (recommended? where?) as a memory compaction utility, since it produces a deep copy of the array. This should be better documented and should be tested, since the hot path of passing a single array through unchanged is tempting. (alternatively, Array::DeepCopy might be provided)

See also discussion in PRs:

• GH-37710: [C++][Integration] Add C++ Utf8View implementation  #37792 (comment)
• GH-35344: [C++][Format] Implementation of the LIST_VIEW and LARGE_LIST_VIEW array formats #35345 (comment)

Component(s)

C++

[lidavidm]

IIRC, it's been recommended in mailing list posts whenever the question of copying an array comes up

It's also in Spark https://github.com/apache/spark/blob/60d02b444e2225b3afbe4955dabbea505e9f769c/python/pyspark/sql/connect/client/core.py#L1287

[jorisvandenbossche]

Some previous discussion on this topic (this issue could be considered as a duplicate of that one if we think we want to add an actual utility, instead of only documenting the concat trick):

• [C++][Python] Create utils for deep-copying an Array/ ArrayData #30503

The workaround of concat_arrays is also mentioned for the bug in pickling serializing the full buffers instead of only the sliced buffers: #26685

[bkietz]

Well if we haven't already documented concatenation for this purpose, I'd prefer to provide an explicit deep copy utility

[lidavidm]

Even if it's not formally documented, it's used by other libraries and has been recommended to users before. I don't think we can change it at this point.

[bkietz]

Sure, but to me it still seems better to alias concatenation of a single array to deep_copy and document that