How to dump index for troubleshooting/debugging #54
Comments
cclauss
pushed a commit
to cclauss/whoosh-1
that referenced
this issue
Feb 9, 2024
# Description `ruff format . && ruff --select=I --fix .` Replaces both `black` and `isort` with `ruff` running rapidly in `pre-commit`. This separates automatic formatting changes (this PR) from more manual and syntactical changes (in mchaput#54) to make the latter easier to review and revert if necessary. # Checklist: - [x] I have performed a self-review of my code - [ ] I have added comments to code where it is hard to understand - [ ] I have made corresponding changes to the documentation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there a way to dump the index in order to troubleshoot anomalies? I'm in the process of assessing the options for full-text indexing and I see that searches using
pyluceneare picking up documents whichwhooshis missing, even though, as far as I can tell, the analyzers and other options are the same. I'd prefer to use the pure Python option, but not if it's broken (or abandoned). The documentation forwhooshis a little unsettling, as it points to a mailing list which looks to be overrun by the spammers, and a repository which is defunct. Is @mchaput still alive? Has he walked away from this project? Are there any other maintainers with commit privileges?Thanks!
The text was updated successfully, but these errors were encountered: