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

Change NA handling in JSON conversion #169

Merged
merged 3 commits into from
Dec 9, 2022
Merged

Change NA handling in JSON conversion #169

merged 3 commits into from
Dec 9, 2022

Conversation

juliasilge
Copy link
Member

Closes #167

As show in the above issue ⤴️ we had a problem with how all-NA columns were handled in predict.vetiver_endpoint. With this change, NA values are stored as strings in the JSON passed over in the request body. The test shows how we can now predict with all-NA columns, and the example with xgboost now works.

@juliasilge
Copy link
Member Author

Do you mind giving this a try when you get a chance @btbroderick? You can install it via remotes::install_github("rstudio/vetiver-r@json-na-vals").

@btbroderick
Copy link

btbroderick commented Dec 9, 2022 via email

@juliasilge juliasilge marked this pull request as ready for review December 9, 2022 15:09
@juliasilge
Copy link
Member Author

Thank you for taking a look! 🙌

@juliasilge juliasilge merged commit 651924e into main Dec 9, 2022
@juliasilge juliasilge deleted the json-na-vals branch December 9, 2022 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

predict.vetiver_endpoint errors if all values in column are missing for xgboost model
2 participants