Skip to content
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.

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

Either deprecate or test support for URI inputs like s3. #9470

Closed
trivialfis opened this issue Aug 11, 2023 · 0 comments · Fixed by #9504
Closed

Either deprecate or test support for URI inputs like s3. #9470

trivialfis opened this issue Aug 11, 2023 · 0 comments · Fixed by #9504

Comments

@trivialfis
Copy link
Member

trivialfis commented Aug 11, 2023

Currently, the support for object storage like s3 and hdfs are "best-effort", meaning we write code using dmlc::Stream most of the time but with an exception in external memory support due to the use of mmap. We have no test for related features on our CI. I suggest that we deprecate the use of these features inside XGBoost and let third-party libraries handle them. For instance, to load a model in Python, one can first use a different library to fetch the model from s3 then use Booster to load from a byte buffer. This way, we can limit the scope of the code base to be more aligned with machine learning and have less concern with system programming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant