Filter by reset
- Everywhere
85 - Issues
23 - Pull Requests
18 - Comments
44
We should consider adding logic that will allow us to find similar issues/comments in the same way we do in our Image demo.
est::size_M
Migrate to per-repo storage scheme
Consider enabling bigram_index to improve autocomplete
…Here The autocomplete results could be better if they included native support . It's currently impossible likely because bigram_index is not enabled. If we do it, the results may be better. E.g.: mysql> drop table if exists t; create table t(f text) min_ …
size_S
Show comments on state filter change for those issue state only (JOIN in the demo)
When we work with filters and search, we can currently filter by the state that only issues and pull requests have. However, when we change the state to open or close, we still search for comments everywhere. As discussed before, it would be a good idea …
size_S
Experiment with distributed table
Try to use a distributed table with issue and comment tables in it and CALL AUTOCOMPLETE on it to validate whether it works as expected or not.
Migrate to per-repo storage scheme
As we discussed here we should try to migrate to table-per-repo scheme: https://github.com/manticoresoftware/manticore-github-issue-search/issues/25#issuecomment-2249352562 To do so we should first implement the logic that will help us dirrectly query the …
Various fixes and improvements to the Demo
Demo: change closed issue/PR color to github's
Enable all full-text search operators
Enable all full-text search operators
Enable all full-text search operators
Prevent 100k+ repos to be added
est::size_S
Change internal architecture of storing data
Change internal architecture of storing data
Change internal architecture of storing data
Change internal architecture of storing data
Long query leads to "Something went wrong"
Change internal architecture of storing data
Long query leads to "Something went wrong"