[ https://issues.apache.org/jira/browse/ASTERIXDB-3091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael J. Carey reassigned ASTERIXDB-3091: ------------------------------------------- Assignee: Ian Maxon > Anonymous types are not always properly cleaned up on DROP TYPE > --------------------------------------------------------------- > > Key: ASTERIXDB-3091 > URL: https://issues.apache.org/jira/browse/ASTERIXDB-3091 > Project: Apache AsterixDB > Issue Type: Bug > Components: MTD - Metadata > Affects Versions: 0.9.6, 0.9.7, 0.9.8, 0.9.9 > Reporter: Michael J. Carey > Assignee: Ian Maxon > Priority: Critical > Attachments: Screen Shot 2022-11-27 at 11.27.26 PM.png > > > Sometimes when a datatype with nested anonymous content is dropped the > anonymous types that the system creates in response to CREATE TYPE are left > behind - still present - after doing DROP TYPE on the offending type. I just > saw this happen for the following type: > CREATE TYPE UserType AS { > _oid: uuid, > user_id: string, > email: string, > name: { first: string?, last: string? }, > address: { street: string?, city: string?, state: string?, zip: int? }?, > categories: [ string ], > phone: [ { number: string?, kind: string? } ], > joined_date: string, > is_buyer: boolean, > is_seller: boolean > }; > DROP TYPE UserType; > I am able to reproduce this on the version of AsterixDB being used by my > CS220P class (which is only slightly behind master in the area of type-y > stuff). -- This message was sent by Atlassian Jira (v8.20.10#820010)