Skip to content

[FSTORE-1858] Fix the incorrect statement about hsfs and hsml packages #517

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 30, 2025
Merged

[FSTORE-1858] Fix the incorrect statement about hsfs and hsml packages #517

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/user_guides/migration/40_migration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,11 +19,11 @@ A number of significant changes have been made in the Python API
Hopsworks 4.0. Previously, in Hopsworks 3.X, there were 3 python
libraries used (“hopsworks”, “hsfs” & “hsml”) to develop feature,
training & inference pipelines, with the 4.0 release there is now
one single “hopsworks” python library that can should be used. For
backwards compatibility, it will still be possible to import both
the “hsfs” & “hsml” libraries but these are now effectively aliases
to the “hopsworks” python library and their use going forward should
be considered as deprecated.
one single “hopsworks” python library that should be used. For
backwards compatibility, it is still possible to import both
the “hsfs” & “hsml” packages directly, but the proper way to
import them is to use “hopsworks.hsfs” & “hopsworks.hsml”.
The direct imports will be deprecated later.

Another significant change in the Hopsworks Python API is the use of
optional extras to allow a developer to easily import exactly what is
Expand Down