You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
As noted at the end of #3422 deleting and purging a dataset still results in datastore tables that are unreferenced.
Steps to reproduce
on a configuration with datapusher enabled upload a dataset with csv tables delete and purge that dataset then recreate it with additional csv lines
Expected behavior
1 table in datastore
**Actual behavior *
current and previous tables in datastore
Additional details
We have a set of csv files from iot sensors the csv files have time series data with real time additions every x minutes every day we drop all these datasets and re-injest them into ckan.
the complete dataset of all data in the system is ~200Mb however our datastore_default is 12Gb after running for a month or so
The text was updated successfully, but these errors were encountered:
firstnevyn
changed the title
Delete and purging a dataset leaves unreferenced datastore tables
Delete and resources leaves unreferenced datastore tables
Jan 28, 2022
like in #3425 we could hook the IPackageController after_delete to handle package deletion, then chain the dataset_purge action to handle the purge case.
CKAN version
2.9.4
Describe the bug
As noted at the end of #3422 deleting and purging a dataset still results in datastore tables that are unreferenced.
Steps to reproduce
on a configuration with datapusher enabled upload a dataset with csv tables delete and purge that dataset then recreate it with additional csv lines
Expected behavior
1 table in datastore
**Actual behavior *
current and previous tables in datastore
Additional details
We have a set of csv files from iot sensors the csv files have time series data with real time additions every x minutes every day we drop all these datasets and re-injest them into ckan.
the complete dataset of all data in the system is ~200Mb however our datastore_default is 12Gb after running for a month or so
The text was updated successfully, but these errors were encountered: