Redash: Add ability to delete a query

[akaul]

Add the ability to delete a query via the frontend

• For query owner, they should have the ability to delete their own query. Oftentimes, new users create test queries which are quickly abandoned.
• For admins, they should have the ability to delete any query to enable malformed/bad queries to be removed.

[arikfr]

Currently you can archive a query from the UI. It removes it form all dashboards and from search results. It practically the same as deleting except that you still have a database record.

Isn't this enough?

[akaul]

If a re:dash report has been shared with individuals, they can still access an archived query if they have a direct link to the query. In the testing I performed, it's also possible to run these archived queries against the database. I'm not sure if this is a shortcoming of the archival feature or if this demands a new delete feature.

Ideally, it'd be great to have the ability to delete a query as well as not be able to run archive queries.

[FsecureSamiTikka]

It seems to me that an archived query can still keep referring to rows in query_results table. I have in query_results some rows where retrieved_at is from year 2016. I would like to make sure cached data in query_results is deleted in a timely manner.

[atharvai]

I think a better solution might be to not allow archived queries to execute. That way even if they show old results, it can't be updated.

Secondly, you can go to redash_url/admin and search for queries there to delete

[mrjk05]

+1 on the ability to delete queries. Archiving a query isn't enough as the data can still be accessed.
There are cases (like I'm in with privacy and financial services) that I need to ensure that no one at the company shouldn't get access to a query result. Deleting the query is the best way to prevent this.

[arikfr]

@mrjk05,

Archiving a query isn't enough as the data can still be accessed.
There are cases (like I'm in with privacy and financial services) that I need to ensure that no one at the company shouldn't get access to a query result.

One workaround you can use right now is to change query text + execute query before archiving.

Of course this is not ideal, so if anyone wants to take a stab at implementing this functionality they are welcome to.

[dharamgajera]

Any Update on this ?

[ivangretsky]

Good day!

Seems like a basic functionality (which should be implemented out of the box from the start). Is there anything we do not see that makes it hard or not desirable to implement?