Azure-docs: spell check is not working for the api call as it throws an error to remove spell check from the service

[xtianus79]

here is the direct error which contradicts the information in this article:

{
"error": {
"code": "BadArgument",
"message": "The application xxxxxx-5e70-48dd-xxxxsxxxxx cannot be packaged for the STAGING slot due to having unsupported features. In order to be able to package the application, please do the following:Remove the spell checker publish setting and republish.\r\n"
}
}

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: cc19d2e0-5960-c165-083c-a9dcf9976c91
• Version Independent ID: 58d32965-6909-2461-5158-aa66d904bf3c
• Content: Docker containers - LUIS - Azure Cognitive Services
• Content Source: articles/cognitive-services/LUIS/luis-container-howto.md
• Service: cognitive-services
• Sub-service: language-understanding
• GitHub Login: @IEvangelist
• Microsoft Alias: dapine

[YutongTie-MSFT]

@xtianus79
Thanks for the feedback! We are currently investigating and will update you shortly.

[YutongTie-MSFT]

@xtianus79 Hi, could you please send us an email with your Azure Subscription ID and URL of this thread to [email protected] ? We would like to investigate deeply. Thanks.

[YutongTie-MSFT]

@xtianus79 Hi, we have not received your email. Please send us an email if you still face this issue. I am going to close this since it's not a document issue. Thank you.
We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.

[xtianus79]

@YutongTie-MSFT I am pretty sure this persists but let me check

[xtianus79]

i am going to post this here and send the email. However the issues still persist and this is kind of issue for publication. meaning does bing spell check work on a container or not?

[xtianus79]

@YutongTie-MSFT can you reopen the thread until there is a resolution to the issue?

[YutongTie-MSFT]

@IEvangelist Hi David, could you please help us check this issue?

@xtianus79 Thank you for your information, I will reopen it.

[cahann]

Spell check is not supported out of the box in containers

[xtianus79]

@cahann does that contradict the documentation which says this:

https://docs.microsoft.com/en-us/azure/cognitive-services/luis/luis-container-howto

Supported dependencies for latest container
The latest container, released at 2019 //Build, will support:

Bing spell check: requests to the query prediction endpoint with the &spellCheck=true&bing-spell-check-subscription-key={bingKey} query string parameters. Use the Bing Spell Check v7 tutorial to learn more. If this feature is used, the container sends the utterance to your Bing Spell Check V7 resource.
New prebuilt domains: these enterprise-focused domains include entities, example utterances, and patterns. Extend these domains for your own use.

[IEvangelist]

I'm experiencing the same issue, and I would have expected this to work. I'm sharing this issue with the dev team and will report back the next steps. I'm assuming they will create an issue internally to track this effort.

[IEvangelist]

This is unfortunately not supported and there was a mistake in the docs. #please-close

[xtianus79]

@IEvangelist this is a major deal here. Where would be the best place to illustrate a concern about the feature that our team was planning on using may now not be possible? The need is this, if we have a luis container that has luis cognitive services you're saying using a spellcheck key for the request api is not possible?

[IEvangelist]

@IEvangelist this is a major deal here. Where would be the best place to illustrate a concern about the feature that our team was planning on using may now not be possible? The need is this, if we have a luis container that has luis cognitive services you're saying using a spellcheck key for the request api is not possible?

I'm working with the team to determine what might have happened, I'm not certain what to say right now. I'll report back as soon as I know more.

[cahann]

Apology for the confusion but in both cases LUIS container will be calling external service (aka bing spell check) for spell correct which is a step the can easily happen as preprocessing step before calling LUIS.

[IEvangelist]

Hi @xtianus79,

We are working to get the container updated, and we will hopefully have this fixed in the next release of the container -- in a week or two.

[xtianus79]

@IEvangelist awesome!!! When you say, "Get the container updated," what do you mean exactly? Does this mean the repository the container can pull the Luis instance from? So this would be an updated docker Luis pull?

Also, where can we follow the release of these features and addons?

Lastly, what does this mean in the sense of how the bing service will work from the container. Meaning, when this update is made will I be able to make a query to the luis / qna services that will have the bing spell check key parameter work for the Luis query?

[xtianus79]

@cahann Are you saying the bing spell check service won't be in the same cognitive service container as the Luis container? This would be very counterproductive to the on-prem solution we trying to achieve. I would like to have clarity on this as much as possible. In the next update for the container what does that mean exactly.

In general there are vital parts and pieces that when you make the heart and brains on-premise but no other vital services that correlate with it makes the entire solution more difficult to pursue.

Is it possible to have an internal discussion that illustrates this point? If you make Luis containerizable you have other parts that must be in association with that paradigm. The spell check is certainly one of those pieces.

[IEvangelist]

@IEvangelist awesome!!! When you say, "Get the container updated," what do you mean exactly? Does this mean the repository the container can pull the Luis instance from? So this would be an updated docker Luis pull?

Also, where can we follow the release of these features and addons?

Lastly, what does this mean in the sense of how the bing service will work from the container. Meaning, when this update is made will I be able to make a query to the luis / qna services that will have the bing spell check key parameter work for the Luis query?

Hi @xtianus79,

The container is periodically updated, and it is not currently announced. The updates are usually minor and typically never include breaking changes. We're working on providing more clarity into this process. I'll try to post here when the container is updated with the fix.

[cahann]

@cahann Are you saying the bing spell check service won't be in the same cognitive service container as the Luis container? This would be very counterproductive to the on-prem solution we trying to achieve. I would like to have clarity on this as much as possible. In the next update for the container what does that mean exactly.

In general there are vital parts and pieces that when you make the heart and brains on-premise but no other vital services that correlate with it makes the entire solution more difficult to pursue.

Is it possible to have an internal discussion that illustrates this point? If you make Luis containerizable you have other parts that must be in association with that paradigm. The spell check is certainly one of those pieces.

Unfortunately, we depend on bing spell check so getting it to run on containers is out of out scope. We are exploring other spell check options but no ETA yet

[xtianus79]

@cahann thank you