GH-37045: [MATLAB] Implement featherwrite in terms of arrow.internal.io.feather.Writer #37047
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
+1 |
github-actions
bot
added
awaiting merge
|
Lint failure is unrelated to the changes in this PR. |
|
After merging your PR, Conbench analyzed the 5 benchmarking runs that have been run so far on merge-commit e90c316. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
This was referenced Aug 16, 2023
kevingurney
added a commit
that referenced
this pull request
Aug 16, 2023
…de (#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. * Closes: #37203 Lead-authored-by: Sarah Gilmore <sgilmore@mathworks.com> Co-authored-by: Kevin Gurney <kgurney@mathworks.com> Signed-off-by: Kevin Gurney <kgurney@mathworks.com>
loicalleyne
pushed a commit
to loicalleyne/arrow
that referenced
this pull request
Nov 13, 2023
…ernal.io.feather.Writer (apache#37047) ### Rationale for this change Now that apache#37043 is merged, we can re-implement `featherwrite` in terms of the new `arrow.internal.io.feather.Writer` class. Once this change is made, we can delete the legacy build infrastructure and featherwrite MEX code. ### What changes are included in this PR? 1. Re-implemented `featherwrite` using `arrow.internal.io.feather.Writer`. ### Are these changes tested? 1. Yes, the existing tests in `tfeather.m` cover these changes. 2. I had to update some of the expected error message IDs in `tfeather.m` because the new implementation throws errors with different IDs. 3. `featherwrite` used to export the real part of MATLAB complex numeric arrays. The new version of `featherwrite` now errors if the input table contains complex data because feather/Arrow itself does not support complex numeric data. We think this is the right decision. Writing out only the real part is lossy. ### Are there any user-facing changes? Yes, `featherwrite` no longer supports writing complex numeric arrays. ### Future Directions 1. Once this PR is merged, we will remove the legacy build infrastructure and MEX code. * Closes: apache#37045 Authored-by: Sarah Gilmore <sgilmore@mathworks.com> Signed-off-by: Kevin Gurney <kgurney@mathworks.com>
loicalleyne
pushed a commit
to loicalleyne/arrow
that referenced
this pull request
Nov 13, 2023
…and code (apache#37204) ### Rationale for this change Now that `featherread` and `featherwrite` have been re-implemented in terms of the new MATLAB Interface APIs (apache#37163 and apache#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, apache#27758 has already been implemented and submitted with a different issue attached. * Closes: apache#37203 Lead-authored-by: Sarah Gilmore <sgilmore@mathworks.com> Co-authored-by: Kevin Gurney <kgurney@mathworks.com> Signed-off-by: Kevin Gurney <kgurney@mathworks.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rationale for this change
Now that #37043 is merged, we can re-implement
featherwritein terms of the newarrow.internal.io.feather.Writerclass. Once this change is made, we can delete the legacy build infrastructure and featherwrite MEX code.What changes are included in this PR?
featherwriteusingarrow.internal.io.feather.Writer.Are these changes tested?
tfeather.mcover these changes.tfeather.mbecause the new implementation throws errors with different IDs.featherwriteused to export the real part of MATLAB complex numeric arrays. The new version offeatherwritenow errors if the input table contains complex data because feather/Arrow itself does not support complex numeric data. We think this is the right decision. Writing out only the real part is lossy.Are there any user-facing changes?
Yes,
featherwriteno longer supports writing complex numeric arrays.Future Directions
featherwritein terms ofarrow.internal.io.feather.Writer#37045