You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 8, 2018. It is now read-only.
Optional because there is an obvious trade-off between storage and querying performance, with winner being dependant on use case. If topics get implemented, this should probably be configurable per topic.
There should also be a way (probably via cli), to index existing logs post factum, as well as a way to delete indexes. This would be useful for performance analysis.
P.S. Forgive me if this has already been considered and rejected -- I could not find anything relevant in Issues or design documents.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
UPD: I see there is a related pull request #123
Consider implementing of text indexing for faster queries, as described here:
https://blog.nelhage.com/2015/02/regular-expression-search-with-suffix-arrays/
Optional because there is an obvious trade-off between storage and querying performance, with winner being dependant on use case. If topics get implemented, this should probably be configurable per topic.
There should also be a way (probably via cli), to index existing logs post factum, as well as a way to delete indexes. This would be useful for performance analysis.
P.S. Forgive me if this has already been considered and rejected -- I could not find anything relevant in Issues or design documents.
The text was updated successfully, but these errors were encountered: