Sync Postgres Updates with Solr

[jkmarx]

Reproduce

1. Locally in the admin interface http://192.168.50.50:8000/admin, delete an analysis. (Please note the uuid and which dataset it belongs to.)
2. Locally in the regular view http://192.168.50.50:8000/#/ , go to the dataset browser
3. Click on the analysis filter

Observed

Note, all the 0 were previously deleted analyses. The analysis with 1, I just deleted and Solr still maintains the info.

Expected

Deleted analyses to not show in the filter.

[scottx611x]

Related with #711 #710

[jkmarx]

I was able to clean up the old analyses by deleting and reindexing. ./manage.py rebuild_index --using=data_set_manager --batch-size=25

[scottx611x]

According to @flekschas : "This is probably caused by the fact that Solr's index is not destroyed when running vagrant destroy. To avoid it: either delete the vm completely or rebuild / drop Solr's index."

[scottx611x]

@fritz You mentioned that you have performed something along these lines before. Could you point me to that code?

[flekschas]

@scottx611x
Yep for the datasets. For example when you delete a dataset the pre_delete signal will trigger an index update:

1. Signal: https://github.com/parklab/refinery-platform/blob/develop/refinery/core/models.py#L601
2. Deletion: https://github.com/parklab/refinery-platform/blob/develop/refinery/core/utils.py#L198-L203

[hackdna]

Any considerations for pre_delete vs post_delete?

[flekschas]

How do you want to access the dataset instance after it was deleted?

[hackdna]

So, pre_delete must be used?

[scottx611x]

The fix from commit: 1c25ce3 seems to work only 90% of the time.
Once in a while upon Analysis deletion something remains within Solr.

See:

Currently looking into this