Not having looked at this repo for a few months, I've discovered some issues which cause confusion:
1) empty values in the database (null) display as the string 'null' and not as a blank field (e.g., the string ''),
2) The micro-service caches the database connection which it only uses when new data is uploaded and the ElasticSearch index is updated from the database. This can cause failures if the database is bounced (as it has been). A more graceful way of dealing with this problem is now being created and tested.
ChuckKollar
commented
5 months ago
Not having looked at this repo for a few months, I've discovered some issues which cause confusion: 1) empty values in the database (null) display as the string 'null' and not as a blank field (e.g., the string ''), 2) The micro-service caches the database connection which it only uses when new data is uploaded and the ElasticSearch index is updated from the database. This can cause failures if the database is bounced (as it has been). A more graceful way of dealing with this problem is now being created and tested.