-
Notifications
You must be signed in to change notification settings - Fork 274
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
version 2.2.0 gives pgml.predict is not unique #549
Comments
This is due to ambiguity with the single tuple version of predict added for preprocessing when there is a single raw feature argument. This used to work a bit by accident, as the smallint[] and broader feature float4[] were both flattened into a single array. I'll look at what we can do to disambiguate, it maybe as easy as adding explicit predict functions for each type of numeric feature array to provide exact matches and disambiguate, but I'd rather see if we can do something smarter, to disambiguate based on the preprocessing directives, in addition to the types. |
any progress on this? :) it makes using preprocessing feature rather unusable |
I'm worried about this ambiguity in the APIs, since you mention it makes preprocessing unusable. To clarify,
The syntax distinction is subtle enough that people may overlook it, and call the wrong version. I'm curious if this was biting you, or just the areas in the notebooks that were not explicitly cast to FLOAT4? |
Thanks for the update, not just the stuff from the notebooks, thats what I tried in the end to make sure I was not doing something wrong in my own project. I try to run some predictions on my own data but it needs to be preprocessed because of the NULLs and categorical variables. I will try now with the adjusted api.rs hope it works. |
New version installed from the apt repo gives error such as:
error returned from database: function pgml.predict(unknown, smallint[]) is not unique
Caused by:
function pgml.predict(unknown, smallint[]) is not unique
even for the most of the examples in the notebooks section.
The text was updated successfully, but these errors were encountered: