Hi. I'm not sure if this is the correct repository to post to, but it looked the closest.
I'm experiencing what appears to be a bug with the endpoints exposed by Azure ML. I've created a very simple experiment that takes a db query as input to an "Import Data"-Module:
When deployed as a web service (classic), it works with both response-request and batch calls. However, if I create a new endpoint for the web service, Response-Request no longer works, and I get the following error. Note that Batch requests do work on this new endpoint.
I'm not entirely sure if there's something I'm missing or if there's just a bug here, but it seems to be the latter. Any input would be greatly appreciated.
Hi. I'm not sure if this is the correct repository to post to, but it looked the closest.
I'm experiencing what appears to be a bug with the endpoints exposed by Azure ML. I've created a very simple experiment that takes a db query as input to an "Import Data"-Module:
When deployed as a web service (classic), it works with both response-request and batch calls. However, if I create a new endpoint for the web service, Response-Request no longer works, and I get the following error. Note that Batch requests do work on this new endpoint.
I'm not entirely sure if there's something I'm missing or if there's just a bug here, but it seems to be the latter. Any input would be greatly appreciated.
(Corresponding SO thread here: http://stackoverflow.com/questions/41595002/azure-machine-learning-endpoint-sql-access-fails-works-in-experiement)