sgilmore10 opened a new pull request, #37204:
URL: https://github.com/apache/arrow/pull/37204
### Rationale for this change
Now that `featherread` and `featherwrite` have been re-implemented in terms
of the new MATLAB Interface APIs (#37163 and #37047), we can remove the unused
feather V1 MEX infrastructure and code.
### What changes are included in this PR?
1. Deleted the following source and header files that are specific to the
feather V1 MEX implementation:
- `arrow/matlab/src/cpp/arrow/matlab/feather/feather_functions.[cc][h]`
- `arrow/matlab/src/cpp/arrow/matlab/feather/feather_reader.[cc][h]`
- `arrow/matlab/src/cpp/arrow/matlab/feather/feather_writer.[cc][h]`
- `arrow/matlab/src/cpp/arrow/matlab/feather/matlab_traits.h`
- `arrow/matlab/src/cpp/arrow/matlab/feather/util/handle_status.[cc][h]`
-
`arrow/matlab/src/cpp/arrow/matlab/feather/util/unicode_conversion.[cc][h]`
- `arrow/matlab/src/cpp/arrow/matlab/mex/call.cc`
- `arrow/matlab/src/cpp/arrow/matlab/mex/mex_functions.h`
- `arrow/matlab/src/cpp/arrow/matlab/mex/mex_util.[cc][h]`
- `arrow/matlab/src/cpp/arrow/matlab/mex/mex_util_test.cc`
- `arrow/matlab/src/cpp/arrow/matlab/api/visibility.h`
2. Deleted the following feather V1 MEX-specific build infrastructure files:
- `arrow/matlab/build_support/common_vars.m`
- `arrow/matlab/build_support/compile.m`
- `arrow/matlab/build_support/test.m`
3. Removed all feather V1 MEX-specific logic from the
`arrow/matlab/CMakeLists.txt` file.
### Are these changes tested?
No tests are needed. The old feather V1 MEX specific implementation is
unused code.
### Are there any user-facing changes?
No.
### Future Directions
1. Review the back-log of stale tasks/issues that are no longer actionable
and close them. For example, #27758 has already been implemented and submitted
with a different issue attached.
--
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]
