sgilmore10 opened a new pull request, #37613:
URL: https://github.com/apache/arrow/pull/37613

   <!--
   Thanks for opening a pull request!
   If this is your first pull request you can find detailed information on how 
   to contribute here:
     * [New Contributor's 
Guide](https://arrow.apache.org/docs/dev/developers/guide/step_by_step/pr_lifecycle.html#reviews-and-merge-of-the-pull-request)
     * [Contributing 
Overview](https://arrow.apache.org/docs/dev/developers/overview.html)
   
   
   If this is not a [minor 
PR](https://github.com/apache/arrow/blob/main/CONTRIBUTING.md#Minor-Fixes). 
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](http://theapacheway.com/open/#:~:text=Openness%20allows%20new%20users%20the,must%20happen%20in%20the%20open.)
 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}
   
   -->
   
   ### Rationale for this change
   
   Currently, there is no way to easily convert an `arrow.array.ChunkedArray` 
into a corresponding MATLAB array, other than (1) manually iterating chunk by 
chunk, (2) calling `toMATLAB` on each chunk, and then (3) concatenating all of 
the converted chunks together into one contiguous MATLAB array.
   
   It would be helpful to add a toMATLAB method to `arrow.array.ChunkedArray` 
that abstracts away all of these steps.
   
   ### What changes are included in this PR?
   
   1. Added `toMATLAB` method to `arrow.array.ChunkedArray` class
   2. Added `preallocateMATLABArray` abstract method to `arrow.type.Type` 
class. This method is used by the `ChunkedArray` `toMATLAB` to pre-allocate a 
MATLAB array of the expected class type and shape. This is necessary to ensure 
`toMATLAB` returns the correct MATLAB array when the `ChunkedArray` has zero 
chunks. If `toMATLAB` stored the result of calling `toMATLAB` on each chunk in 
a `cell` array before concatenating the values, `toMATLAB` would return a 0x0 
`double` array for zero-chunked arrays. The pre-allocation approach avoids this 
issue.
   3. Implement `preallocateMATLABArray` on all `arrow.type.Type` classes.
   4. Added an abstract class `arrow.type.NumericType` that all classes 
representing numeric data types inherit from. `NumericType` implements 
`preallocateMATLABArray` for its subclasses.
   
   ### Are these changes tested?
   
   Yes. Added unit tests to `tChunkedArray.m`.
   
   ### Are there any user-facing changes?
   
   Yes. Users can now call `toMATLAB` on `ChunkedArray`s.
   
   **Example**
   
   ```matlab
   
   >> a = arrow.array([1 2 NaN 4 5]);
   >> b = arrow.array([6 7 8 9 NaN 11]);
   >> c = arrow.array.ChunkedArray.fromArrays(a, b);
   >> data = toMATLAB(c)
   
   data =
   
        1
        2
      NaN
        4
        5
        6
        7
        8
        9
      NaN
       11
   
   
   ```
   <!--
   If there are user-facing changes then we may require documentation to be 
updated before approving the PR.
   -->
   
   <!--
   If there are any breaking changes to public APIs, please uncomment the line 
below and explain which changes are breaking.
   -->
   <!-- **This PR includes breaking changes to public APIs.** -->
   
   <!--
   Please uncomment the line below (and provide explanation) if the changes fix 
either (a) a security vulnerability, (b) a bug that caused incorrect or invalid 
data to be produced, or (c) a bug that causes a crash (even when the API 
contract is upheld). We use this to highlight fixes to issues that may affect 
users without their knowledge. For this reason, fixing bugs that cause errors 
don't count, since those are usually obvious.
   -->
   <!-- **This PR contains a "Critical Fix".** -->


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to