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

Output Schema Doesn't Respect Type #14

Open
csteegz opened this issue Oct 30, 2019 · 1 comment
Open

Output Schema Doesn't Respect Type #14

csteegz opened this issue Oct 30, 2019 · 1 comment
Labels
enhancement New feature or request

Comments

@csteegz
Copy link

csteegz commented Oct 30, 2019

Summary

If you pass a pandas type to output schema, and return a pandas dataframe from my run function, the generated code will not be automatically encoded.

What do you expect

Azure ML will encode my output to json.

What actually happens

The service will report an error encoding the dataframe.

@trangevi trangevi added the enhancement New feature or request label Oct 30, 2019
@trangevi
Copy link
Member

In a best effort to keep this separate from AML, it isn't the job of the AML service to encode the output to JSON (or the other way around in the case of input). For input, that is one of the value adds for the decorator though, is to allow type transformations, and AML users can take advantage of that fact.

Our original thinking was that we didn't want to fail a call to the decorated function because of a datatype transformation issues after the function was called, but I can see the value to allowing for this (as well as for maintaining consistency). Will take a look at adding this in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants