Fix eval_set preprocessing for XGBoost estimators with categorical features#1470
Merged
Fix eval_set preprocessing for XGBoost estimators with categorical features#1470
Conversation
Co-authored-by: thinkall <3197038+thinkall@users.noreply.github.com>
…atures Co-authored-by: thinkall <3197038+thinkall@users.noreply.github.com>
Co-authored-by: thinkall <3197038+thinkall@users.noreply.github.com>
Co-authored-by: thinkall <3197038+thinkall@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix eval_set preprocessing for XGBRegressor
Fix eval_set preprocessing for XGBoost estimators with categorical features
Jan 10, 2026
thinkall
approved these changes
Jan 20, 2026
jianglibigdata
approved these changes
Jan 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using
flaml.default.XGBClassifierorXGBRegressorwith categorical features and aneval_setparameter, the validation data was not preprocessed, causing feature_names mismatch errors. FLAML's preprocessing reorders columns (categorical columns first), but this transformation was only applied to training data.Changes
flaml/default/estimator.py: Added eval_set preprocessing in thefitmethodself._feature_transformerself._label_transformerwhen applicable (for rf, extra_tree, xgboost estimators)test/default/test_defaults.py: Extendedtest_xgboost()with categorical feature eval_set testsExample
Original prompt
This section details on the original issue you should resolve
<issue_title>[Bug]: flaml.default.XGBRegressor does not preprocess eval_set</issue_title>
<issue_description>### Describe the bug
Sometimes (when there are cat columns, for example) flaml (at least zero-shot) re-arranges columns. But for XGBRegressor/XGBClassifier, it misses to do that for the validation dataframe.
Steps to reproduce
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.