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

"context" parameter automatically set back to default value when using the python sdk #34623

Closed
johannesgoldbeck opened this issue Mar 5, 2024 · 6 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. issue-addressed The Azure SDK team member assisting with this issue believes it to be addressed and ready to close. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Search

Comments

@johannesgoldbeck
Copy link

Type of issue

Code doesn't work

Description

I am managing my Azure AI skillset via the python SDK. When using the EntityRecognitionSkill, I set the context parameter of the class to "/document/pages/*", since I want the Entity Extraction for each page of the document.
When I use the create_or_update_skillset method of the SearchIndexerClient class to update my skillset it will throw no errors, but the context parameter of the Entity Recognition Skill will be set back to its default value "/document", which I can see in the json of the skillset displayed in the Azure Portal. I have to change it manually in the Portal, s.t. the skill will be executed without error when indexing.

Page URL

https://learn.microsoft.com/en-us/python/api/azure-search-documents/azure.search.documents.indexes.models.entityrecognitionskill?view=azure-python

Content source URL

https://github.com/MicrosoftDocs/azure-docs-sdk-python/blob/main/docs-ref-autogen/azure-search-documents/azure.search.documents.indexes.models.EntityRecognitionSkill.yml

Document Version Independent Id

3a3ff14f-2b0e-c83f-0e51-f48136ff7a15

Article author

@lmazuel

Metadata

  • ID: d674ff86-de21-e3e3-c363-96b5e35bd829
@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-triage This issue needs the team to triage. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Search labels Mar 5, 2024
@kashifkhan
Copy link
Member

Thank you for the feedback @johannesgoldbeck . We will investigate and get back to you asap.

Could you also provide some sample code that can help repro the issue ?

@kashifkhan kashifkhan added needs-author-feedback More information is needed from author to address the issue. and removed needs-team-triage This issue needs the team to triage. labels Mar 5, 2024
Copy link

github-actions bot commented Mar 5, 2024

Hi @johannesgoldbeck. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

@github-actions github-actions bot added needs-team-attention This issue needs attention from Azure service team or SDK team and removed needs-author-feedback More information is needed from author to address the issue. labels Mar 6, 2024
@johannesgoldbeck
Copy link
Author

This my skill:
image

This my Request to Create/Update the skillset:
image

@xiangyan99 xiangyan99 added the issue-addressed The Azure SDK team member assisting with this issue believes it to be addressed and ready to close. label Mar 7, 2024
@github-actions github-actions bot removed the needs-team-attention This issue needs attention from Azure service team or SDK team label Mar 7, 2024
Copy link

github-actions bot commented Mar 7, 2024

Hi @johannesgoldbeck. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.

@johannesgoldbeck
Copy link
Author

Yea thank YOU for the assistance when it seems like I found a super obvious bug in your code I am paying a shit ton of money to use. I was just wasting ages looking into my code to find the mistake because of which I could not properly deploy the service, but ok.

Can you tell me, when your fix will be deployed?

Copy link

Hi @johannesgoldbeck, since you haven’t asked that we /unresolve the issue, we’ll close this out. If you believe further discussion is needed, please add a comment /unresolve to reopen the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. issue-addressed The Azure SDK team member assisting with this issue believes it to be addressed and ready to close. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Search
Projects
Status: Done
Development

No branches or pull requests

3 participants