3 Commits (f48a863b99a8075da290f9dc85d8296c974fb86b)

Author	SHA1	Message	Date
Jason Song	3b129aaa80	Explain SearchOptions and fix ToSearchOptions (#26542) ... Follow #26012 #26490. A detailed description has been added to the comment.	2 years ago
CaiCandong	0e74fc4a84	Fix project filter bugs (#26490) ... related: #26012 ### Bugs 1. missing project filter on the issue page. 1e76a824bc/modules/indexer/issues/dboptions.go (L11-L15) 3. incorrect SQL condition: some issue does not belong to a project but exists on the project_issue table. f5dbac9d36/models/issues/issue_search.go (L233) ### Before:  ### After:  --------- Co-authored-by: Giteabot <teabot@gitea.io>	2 years ago
Jason Song	1e76a824bc	Refactor and enhance issue indexer to support both searching, filtering and paging (#26012) ... Fix #24662. Replace #24822 and #25708 (although it has been merged) ## Background In the past, Gitea supported issue searching with a keyword and conditions in a less efficient way. It worked by searching for issues with the keyword and obtaining limited IDs (as it is heavy to get all) on the indexer (bleve/elasticsearch/meilisearch), and then querying with conditions on the database to find a subset of the found IDs. This is why the results could be incomplete. To solve this issue, we need to store all fields that could be used as conditions in the indexer and support both keyword and additional conditions when searching with the indexer. ## Major changes - Redefine `IndexerData` to include all fields that could be used as filter conditions. - Refactor `Search(ctx context.Context, kw string, repoIDs []int64, limit, start int, state string)` to `Search(ctx context.Context, options *SearchOptions)`, so it supports more conditions now. - Change the data type stored in `issueIndexerQueue`. Use `IndexerMetadata` instead of `IndexerData` in case the data has been updated while it is in the queue. This also reduces the storage size of the queue. - Enhance searching with Bleve/Elasticsearch/Meilisearch, make them fully support `SearchOptions`. Also, update the data versions. - Keep most logic of database indexer, but remove `issues.SearchIssueIDsByKeyword` in `models` to avoid confusion where is the entry point to search issues. - Start a Meilisearch instance to test it in unit tests. - Add unit tests with almost full coverage to test Bleve/Elasticsearch/Meilisearch indexer. --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>	2 years ago