Delete datasets in pending mode

[kardan]

Context

Users end up with datasets that are in pending mode

Problem or idea

There are issues when importing them and they stay in pending mode.

Solution or next step

We need to make sure we don't introduce bugs in a long-running import. Think We can delete in data_source and let the Postgres cascading to its thing to stay safe - maybe.

• [x] Delete pending datasets
• [x] Delete pending rasters
• [x] Review if we can do a better cleanup
• [x] Remove import bug

[janagombitova]

@kardan are you still working on this one or has everything been already handled?

[tangrammer]

@kardan it seems that we can't remove failing imported dataset

looking at code detail impls, client library view calls GET /api/library and backend then execute this SQL that returns different "things", the problem arises when we try to delete the dataset based on the id received by client-side, but this id is not a dataset-id anymore

[kardan]

I wonder if this relates to https://github.com/akvo/akvo-lumen/issues/1408

[tangrammer]

do you mean #1449 ? thus #1408 is this one 🤔

[tangrammer]

@kardan @janagombitova are you ok if I start with this issue in the meanwhile i get feedback/review from #1744 ?

[tangrammer]

same problem here

in this case DELETE http://t1.lumen.local:3030/api/job_executions/5c7e8f64-4fb2-4b37-906d-4da43760da27 is not even a declared endpoint

[kardan]

@tangrammer I think the DELETE methods are on the different entites (viz, dataset, dashboard). That said, maybe we have nothing for rasters :-(

[muloem]

@tangrammer is this fully resolved? If so maybe we can close it

[tangrammer]

nope

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.