Cannot Drop TAG when Dropping Graph - Intended Feature or Bug?

I have been playing around with TAG feature - which is sweet :wink: And understand this is Beta. In my definition statement, I have the following:
CREATE SCHEMA_CHANGE JOB Genealogy_Schema_Job FOR GRAPH Genealogy {

ADD TAG Father DESCRIPTION “Define Role of Parent that is Male”;
ADD TAG GrandFather DESCRIPTION “Define Role of Parent Father that is Male”;
ADD TAG Mother DESCRIPTION “Define Role of Parent that is Female”;
ADD TAG GrandMother DESCRIPTION “Define Role of Parent Mother is Female”;

The issues is that when I drop the Graph Genealogy, I would assume that the TAGS will go away. They don’t, I have to perform a ‘drop all’ to get rid of them.

Is that the intended behavior to treat TAG as a Global feature?, if I ‘add’ inside a SCHEMA_CHANGE I would assume the scope is limited to the Graph and not Global, as this is the same behavior that I experience with Vertices and Edges.

Any insights would be greatly appreciated.

Mitch

Hi @demit733 I’ll bring this to the internal TigerGraph team. I will try to replicate the same issue. What version of TigerGraph are you running? Are you using docker or cloud?

I’m running TigerGraph version 3.4.0 under Docker version 4.3.2

By the way, if you perform the command: gsql -g $GRAPH_NAME show tag “*”. It will not show the TAGS, but they are still there…If you create and delete your Graph several times, you will hit the 64 TAG limit.