REWORK Restricted Word Solr Admin Interface
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Currently the SOLR Admin interface is broken. When we insert/create/delete records from the UI, the UI times out, gets an internal server error and data is deleted from the following tables.
This code was working for many years, but because of volume the code breaks half way through the reload.
Richard has an idea how to fix it.
Currently the data is loaded into memory and edited.
Then the database tables are deleted and the memory data is written to the new blank tables.
We need to write the data to temp tables first and if they are successfully created we can
delete the database tables and rename the temp tables to the correct names.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the SOLR Admin interface flow for inserting, creating, and deleting restricted-word records, especially where database tables are cleared and reloaded. Review the existing in-memory reload behavior and the proposed temporary-table workflow. Done means large operations complete without timing out or returning server errors, and existing data is not lost when reloading fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, javascript, postgres, python
- Domain
- backend, databases, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100