GH-49684: [MATLAB] Introduce deprecation warnings for "legacy" Feather V1 functions featherread and featherwrite

[kevingurney]

Rationale for this change

In response to #49231 and https://lists.apache.org/thread/1npvnhjb1xwz09zh8vnd079zt2q4o08l, this pull request introduces deprecation warnings for the public MATLAB featherread and featherwrite APIs that allow reading and writing "legacy" Feather V1 files.

The solution of introducing deprecation warnings follows the pyarrow approach proposed in #49590.

Examples

featherread

>> featherread("out.feather")
Warning: Reading from Feather V1 files is deprecated. Use arrow.io.ipc.RecordBatchFileReader to read from Feather V2 (Arrow IPC) files.
> In featherread (line 30)

featherwrite

>> featherwrite("out.feather", array2table(1))
Warning: Writing to Feather V1 files is deprecated. Use arrow.io.ipc.RecordBatchFileWriter to write to Feather V2 (Arrow IPC) files.
> In featherread (line 31)

What changes are included in this PR?

1. Introduced a new warning with identifier arrow:io:feather:v1:FeatherWriteDeprecated when calling featherwrite.m.
2. Introduced a new warning with identifier arrow:io:feather:v1:FeatherReadDeprecated when calling featherread.m.

Are these changes tested?

Yes.

1. Updated matlab/test/tfeather.m to suppress featherread and featherwrite deprecation warnings.
2. Added two new test cases to tfeather.m: VerifyFeatherReadDeprecationWarning and VerifyFeatherWriteDeprecationWarning. These test cases verify that the expected deprecation warnings are issued as expected.
3. Updated matlab/test/arrow/io/feather/tRoundTrip.m to suppress featherread deprecation warnings.

Are there any user-facing changes?

Yes.

1. The featherread and featherwrite functions are user-facing. With these changes, deprecation warnings will be displayed when invoking either of these functions. Note: these warnings can be turned off in MATLAB by calling warning("off", "arrow:io:feather:v1:FeatherWriteDeprecated") and warning("off", "arrow:io:feather:v1:FeatherReadDeprecated").

Future Directions

1. We may want to consider moving featherread and featherwrite into a package like arrow.io.feather.v1.* to mirror the rest of the mlarrow APIs. Alternatively, we could consider removing these functions entirely.

Notes

1. Thank you @sgilmore10 for your help with this pull request!

• GitHub Issue: [MATLAB] Introduce deprecation warnings for "legacy" Feather V1 functions featherread and featherwrite #49684

[github-actions]

⚠️ GitHub issue #49684 has been automatically assigned in GitHub to PR creator.

[kou]

+1

[kevingurney]

+1

[kevingurney]

I recently switched to a new machine, and it looks like my Git email was configured incorrectly for the commits I made to this branch.

I rebased, squashed the old commits, modified my email, and then force pushed to this branch.

I'll wait for the CI checks to pass again and then merge this PR.

Sorry for the confusion!

[kevingurney]

+1