You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose we deprecate the use of text file input and remove the text parsers in XGBoost, including the libsvm parser and csv parser from dmlc core. Nowadays, there's a wealth of third-party libraries focus on feature engineering that can handle these formats with high efficiency. Loading the data inside XGBoost does not provide much value as users are likely need to perform tasks like cross-validation and hyper-parameter optimization.
At the moment, there are three use cases for the text input:
External memory: We have largely replaced the external memory with a custom data iterator. Even with text input, the underlying implementation uses a data iterator.
Federated learning: I believe we will move toward memory input as we progress for better integration with frameworks like nvflare.
The text was updated successfully, but these errors were encountered:
I propose we deprecate the use of text file input and remove the text parsers in XGBoost, including the
libsvm
parser andcsv
parser from dmlc core. Nowadays, there's a wealth of third-party libraries focus on feature engineering that can handle these formats with high efficiency. Loading the data inside XGBoost does not provide much value as users are likely need to perform tasks like cross-validation and hyper-parameter optimization.At the moment, there are three use cases for the text input:
The text was updated successfully, but these errors were encountered: