[BUG]: pyarrow-hotfix is still required even though pyarrow>=14.01

[mdemoret-nv]

Version

24.03

Which installation method(s) does this occur on?

Docker, Conda, Source, Kubernetes

Describe the bug.

After upgrading to cuDF 24.02 in PR #1468, the dependency on pyarrow_hotfix was removed from dependencies.yaml and meta.yaml but __init__.py still calls import pyarrow_hotfix. This causes the runtime container as well as the conda build to fail.

Minimum reproducible example

Run the following:

./docker/build_conda_packages.sh morpheus

And you will see the following in the log:

Relevant log output

Click here to see error details

File "/opt/conda/conda-bld/morpheus-split-24.03.00a/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pl/lib/python3.10/importlib/init.py", line 126, in import_module

return _bootstrap._gcd_import(name[level:], package, level)

File "", line 1050, in _gcd_import

File "", line 1027, in _find_and_load

File "", line 992, in _find_and_load_unlocked

File "", line 241, in _call_with_frames_removed

File "", line 1050, in _gcd_import

File "", line 1027, in _find_and_load

File "", line 992, in _find_and_load_unlocked

File "", line 241, in _call_with_frames_removed

File "", line 1050, in _gcd_import

File "", line 1027, in _find_and_load

File "", line 1006, in _find_and_load_unlocked

File "", line 688, in _load_unlocked

File "", line 883, in exec_module

File "", line 241, in _call_with_frames_removed

File "/opt/conda/conda-bld/morpheus-split-24.03.00a/work/build-conda/morpheus/init.py", line 21, in 

import pyarrow_hotfix

ModuleNotFoundError: No module named 'pyarrow_hotfix'

Full env printout

Click here to see environment details

[Paste the results of print_env.sh here, it will be hidden by default]

Other/Misc.

No response

Code of Conduct

• I agree to follow Morpheus' Code of Conduct
• I have searched the open bugs and have found no duplicates for this bug report