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

Glossary term not visible in Purview #38591

Open
blaine12100 opened this issue Nov 18, 2024 · 1 comment
Open

Glossary term not visible in Purview #38591

blaine12100 opened this issue Nov 18, 2024 · 1 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. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Purview question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@blaine12100
Copy link

  • Package Name: azure.purview.datamap.operations
  • Package Version: 1.0.0b1
  • Operating System: Win 11
  • Python Version: 3.11.0

Describe the bug
When a glossary term is created, it does not show up in the glossary (Classic Type) in purview . I know that the term has been created because when I call the get_terms function, I get the terms that I have created.

To Reproduce
Steps to reproduce the behavior:

  1. Create the glossary using the create function with the request body taken from sample glossary body
  2. Create terms using with request body taken from sample request body with the create_term function

Expected behavior
Glossary terms show up under the classic glossary type in purview (Enterprise glossary is in preview)

Additional context
This issue could be as purview has changed recently and the SDK has not released a new version of this package since the last 3 years or something.

@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-attention Workflow: This issue needs attention from Azure service team or SDK team Purview question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team. labels Nov 18, 2024
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @yifan-zhou922.

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. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Purview question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

1 participant