Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Full-text search #92

Closed
vladimiry opened this issue Jan 7, 2019 · 5 comments
Closed

Full-text search #92

vladimiry opened this issue Jan 7, 2019 · 5 comments

Comments

@vladimiry
Copy link
Owner

The time has come to make it happen. I've started the research and playing around already.

@vladimiry
Copy link
Owner Author

I tried to keep the search index close to the database but it's not going to work well since the index is 3-5x times bigger than the database itself. So the full database serialization takes time, besides the main process might get blocked by expensive serialization/indexing/search actions. So going to try maintaining all the expensive indexing operations in a separate process and save the index in an individual encrypted file like database-index.bin.

@vladimiry
Copy link
Owner Author

vladimiry commented Jan 8, 2019

Since indexing works quite fast I'm also considering not persisting the search index at all but just spawn the separate process which will build the index on app start and keep it up to date while the app is started, so completely in memory only. The implementation would be much simpler and somehow more secure (no addition data persisting).

@vladimiry
Copy link
Owner Author

The initial implementation is going to be released soon.

search

@vladimiry
Copy link
Owner Author

Resolved with v2.2.0 release.

@vladimiry
Copy link
Owner Author

CC @anothernewb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant