quick-pizza-8906
11/09/2021, 2:05 PMUser.UserAccount
and assigned Sensitive
term to field user_id
- then I opened Sensitive
glossary term details and related entities were showing 3 datasets but not mysql User.UserAccount
why is it so? Shouldn't I be able to see this association from that subpage? If not, how can I associate field with a glossary term so that this association is visible both in dataset details and glossary term detail?
2. In local docker deployment I associated a term with a field and then deleted the term via datahub delete ...
command, while the term was gone from the terms UI it was still visible in the dataset details, is there any procedure to trigger removal there as well?big-carpet-38439
11/09/2021, 8:00 PMquick-pizza-8906
11/09/2021, 8:01 PMbig-carpet-38439
11/09/2021, 8:04 PMquick-pizza-8906
11/09/2021, 8:06 PM0.8.16
which I deployed locally via datahub docker...
big-carpet-38439
11/09/2021, 8:07 PMbig-carpet-38439
11/09/2021, 8:07 PMquick-pizza-8906
11/09/2021, 8:08 PMquick-pizza-8906
11/09/2021, 8:10 PMquick-pizza-8906
11/09/2021, 8:10 PMbig-carpet-38439
11/09/2021, 8:13 PMbig-carpet-38439
11/09/2021, 8:14 PM1. Add Sensitive Glossary Term to User.UserAccount
2. Navigate to Sensitive tag
3. View Related Entities
big-carpet-38439
11/09/2021, 8:14 PMquick-pizza-8906
11/09/2021, 8:17 PMquick-pizza-8906
11/09/2021, 8:17 PMquick-pizza-8906
11/09/2021, 8:17 PMbig-carpet-38439
11/09/2021, 8:17 PMquick-pizza-8906
11/09/2021, 8:17 PMbig-carpet-38439
11/09/2021, 8:17 PMquick-pizza-8906
11/09/2021, 8:17 PMquick-pizza-8906
11/09/2021, 8:18 PMquick-pizza-8906
11/09/2021, 8:19 PMquick-pizza-8906
11/09/2021, 8:19 PMbig-carpet-38439
11/09/2021, 8:26 PMbig-carpet-38439
11/09/2021, 8:26 PMquick-pizza-8906
11/09/2021, 8:33 PMbig-carpet-38439
11/09/2021, 9:39 PMbig-carpet-38439
11/09/2021, 9:39 PMbig-carpet-38439
11/09/2021, 9:39 PMrapid-sundown-8805
11/10/2021, 11:52 AMmysterious-butcher-86719
09/20/2022, 1:11 PM