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.
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
Backend agnostic machine learning models #962
Backend agnostic machine learning models #962
Changes from 30 commits
ff2c3e5
b685108
069caa8
f2c5d87
4eedef7
3f64c01
1077aa6
e5a6477
549afef
72c37ff
a300b9d
7704ce2
ab7cc08
8269e56
bbf4dc6
e43710d
9f49f58
331cee0
090d5a9
ebaa2f5
88169f1
c0d37ac
6311a39
a0d6b15
e3f956c
d0d07cf
a1a45f4
63abe98
66af9bd
ad8bf0e
e1ca596
f61131e
9425286
4a30c3c
23022a0
c96d4e8
bfefe83
84cec59
0721c21
c293562
93ff0a1
4717bde
98c42d5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to throw a TODO or FIXME in here to track this failure? Not sure if there's an upstream issue open around this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I opened #1015 and linked to it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if this is something we should fix on the Dask-SQL side (see #1015 (comment)). Would it make sense to have some sort of try/except logic around this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @sarahyurick 🙂 with that additional context, IMO I feel like the best option on our end for now would be to include
cuml.dask.extended.linear_model.logistic_regression.LogisticRegression
in the mapping and raise theImportError
directly, with the idea being that users would just subsequently installdask-glm
into their environment and try rerunning their query.I suppose if we wanted to be as informative as possible, we could reraise the error with some addendum about using the non-Dask equivalent class if installing
dask-glm
isn't an option, though I think that message would probably make more sense to add upstream since it would be informative to cuML users at large.