GH-36560: [MATLAB] Remove the DeepCopy name-value pair from arrow.array.<Numeric>Array constructors

[sgilmore10]

Rationale for this change

We initially added the DeepCopy name-value pair to the numeric array class constructors for testing purposes. When DeepCopy=true, the proxy classes copy the data from the MATLAB array when creating the underlying std::shared_ptr<arrow::NumericArray<CType>>. By default, we don't make a copy and instead store the original array as a property named MatlabArray. Doing so keeps the backing memory of the arrow array alive and avoids a copy.

What changes are included in this PR?

DeepCopy is no longer accepted as a name-value pair by the constructors of the numeric array classes.

Are these changes tested?

No tests were needed.

Are there any user-facing changes?

This is technically a user facing change, but the MATLAB interface is still experimental and under active development. We don't expect anyone to be affected by this change.

• Closes: [MATLAB] Remove the DeepCopy name-value pair from arrow.array.<Numeric>Array constructors  #36560

[github-actions]

Thanks for opening a pull request!

If this is not a minor PR. Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose

Opening GitHub issues ahead of time contributes to the Openness of the Apache Arrow project.

Then could you also rename the pull request title in the following format?

GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

or

MINOR: [${COMPONENT}] ${SUMMARY}

In the case of PARQUET issues on JIRA the title also supports:

PARQUET-${JIRA_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}

See also:

• Other pull requests
• Contribution Guidelines - How to contribute patches

[kou]

+1

[kevingurney]

+1

[kevingurney]

It looks like these changes are ready to be merged. I'll go ahead and merge them now.

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 6 benchmarking runs that have been run so far on merge-commit 5c4ba87.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about possible false positives for unstable benchmarks that are known to sometimes produce them.