Cognite Data Fusion: Is it possible to delete a data set?

Related products: Authentication and Access Management

Is it possible to delete a data set in CDF?

I cannot see any functionality to delete a data set in CDF, either from Fusion, the Python SDK (“This functionality is not yet available in the API.”), or in the API documentation.

I can only see a functionality to archive it. 

 

Kind regards,

Anders Willersrud, Statnett

 

Hi Anders,

That is correct. It is currently not possible to delete a data set, only archive it. Thank you for your question. This functionality is on our backlog, but there is no release data on this functionality yet. 

 

Best regards,

Kevin Gaze Product Manager


Hi Kevin,

thanks for the reply. Please keep us updated if there are any updates on the functionality.

Anders


To be clear @Anders Willersrud, for this feature request,  when you say “delete a data set”, do you mean delete only the data set entity and any  assets, time series, or other entities would remain, but have their data set id set to null or would you expect that deleting a dataset would also delete any data associated with that data set?


Until now this has been relevant when we have created a duplicate data set by mistake, or don’t need an empty data set.

So for a minimum feature request it would be nice if a data set without associated data would be possible to delete.


Yes. Deleting an empty data set should be introduced first.  After that, I propose that the feature to delete a Data Set “Including Data” be introduced.


My proposed backlog order for Product Owner:

  1. Delete of empty data set
  2. Archive of data set including data
  3. Delete of data set including data

 


@Ben Brandt Thank you for following up in this and I agree with your prioritization. 

We will for sure update the community as soon as we have new features planned for data sets. 

Best regards,

Kevin Gaze Product Manager


NewPlanned for development

Planned for developmentGathering Interest

Just so you know, this feature is still on our list, that it jumped into planned for development and back to gathering interest was a mere result of some restructuring in our internal tooling, apologize. 


Gathering InterestPlanned for development