Deleted datasets not deleted

I have deleted the demo analyses and datasets, but a list-data-sets shows these still exist and list-data-set shows they are using Spice. There is also one that I created and deleted. How do I fix this?

Hi @Jeremy_Likezero,

Welcome to QuickSight Community.

When you delete a dataset from the console, it should be removed from the list-data-sets. Just double checking, do you still see the dataset both in the console and in the list-data-sets? If you have more than one region enabled in QuickSight, are you looking at the region where you deleted the datasets?

If you still see this behaviour, I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case. If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf.

Hope this helps!

I have done some more research.

It seems that deleting a dataset (more or less) follows the same paradigm as deleting an analysis, in that it flags it as deleted but does not remove it.

When you delete an analysis in the gui, the “list-analyses” CLI command (list-analyses — AWS CLI 2.15.37 Command Reference) returns a STATUS field that indicates that it is deleted. And, if you delete an analysis in the CLI, by default, it allows an (overridable) 30 day grace period in which you can restore the analysis, after which the analysis is permanently removed.

Whether this grace period is also set by deleting an analysis in the gui is unclear. The “list-analyses” command does not return a “deletion-date” for analyses which are deleted via the gui …

The problem for datasets, is that the json that is returned by the “list-data-sets” CLI command does not include a STATUS field. If you use the “delete-data-set” in the CLI to remove the defunct dataset, it goes permanently.

So, in summary,

  1. There doesn’t appear to be a problem as such. So long as there is some sort of mechanism that cleans up and eventually releases SPICE storage for datasets that the user thinks have gone, then all is good. (Is this the case?)

  2. There is a minor gripe that the list-data-sets command does not include a STATUS field.

J

2 Likes

Thank you for the feedback @Jeremy_Likezero – At AWS, our roadmap is primarily driven by our customers. Your feedback helps us build a better service. I have tagged this as a feature request.