Liam De Lee on Mon, 23 Jul 2018 13:45:23
if i launch the search query "not has:tags" it works as intended if i only have user defined tags. But once i add a glossary tag to a data set i get this one back as well, but i do not want this. Is this some kind of bug? or am i doing something wrong here?
Many thanks in advance
Liam De Lee(Belgiüm)
VairavanS (Azure) on Tue, 24 Jul 2018 18:00:36
It seems like a bug to me. Because glossary tags are tracked as termName, Please take a look at this document, So Please file your bug here for the product team to resolve it.
Liam De Lee on Wed, 25 Jul 2018 06:26:27
I reported it as a bug for the product team. However should it then not be has:termName? this is not working because it does not know termName but maybe it is not a bug but just not implemented?
But it would be a lot better instead of using two not has clauses to ofcourse have it under the not has:tags!
How long will it take for this bug to be fixed? because it is one of our core needs to be able to use data catalog.
thanks for your help already.
VairavanS (Azure) on Wed, 25 Jul 2018 21:24:49
I have reached out to the product team with your query already. I will update this thread as soon as i get a response. Thanks for your patience
Liam De Lee on Fri, 27 Jul 2018 08:21:58
thanks for the support and hope to hear from you soon.
Liam De Lee on Fri, 10 Aug 2018 12:34:40
Do you have any update on this? Because it is becoming a blocking issue for us.
Thanks in Advance
VairavanS (Azure) on Fri, 24 Aug 2018 17:42:17
I got the below update from the product team.
As defined in https://docs.microsoft.com/en-us/rest/api/datacatalog/data-catalog-search-syntax-reference community tags are referenced using tags. Glossary terms are referenced using termName. However there is a bug that "not has:termName" won't work because glossary terms are tracked separately. I don't know if there is a work around.
Liam De Lee on Mon, 27 Aug 2018 06:46:03
Thanks for the update