A long-standing issue with Kithe and GeoBlacklight Admin (and GEOMG beforehand), is that there are situations where you can save an object to the database, but the background process that indexes that record into Solr can fail — usually because of locn_geometry parsing issues.
We need to write a little task to audit the database entries and the solr entries and produce a diff.
This will require a Solr schema config change, to copy geomg_id_s into a docValues field. Afterwards you can run:
http://localhost:8983/solr/blacklight-core/export?q=*:*&sort=geomg_id_sdv+asc&fl=geomg_id_sdv
A long-standing issue with Kithe and GeoBlacklight Admin (and GEOMG beforehand), is that there are situations where you can save an object to the database, but the background process that indexes that record into Solr can fail — usually because of locn_geometry parsing issues.
We need to write a little task to audit the database entries and the solr entries and produce a diff.
Solr's /export handler looks promising: https://solr.apache.org/guide/solr/latest/query-guide/exporting-result-sets.html
This will require a Solr schema config change, to copy geomg_id_s into a docValues field. Afterwards you can run:
http://localhost:8983/solr/blacklight-core/export?q=*:*&sort=geomg_id_sdv+asc&fl=geomg_id_sdv
and results will be JSON like this:
Similarly, we'll want to produce a sorted list of geomg_id_s values from PostgreSQL for comparison.
Which returns...