Last modified: 2014-07-26 09:40:00 UTC
1) you have to use message: prefix 2) it only searches from open commits by default 3) doing message:foo is:merged takes forever
(In reply to comment #0) > 3) doing message:foo is:merged takes forever A lot of queries for is:merged are really slow. I'm curious if this is because the caches are colder for merged changes (since less people are searching them). The following query *also* takes a very long time: "is:merged CodeReview-2" (someone was asking me the other day if it was possible to have submitted a -2) In any case, looks like something we can report upstream.
(In reply to comment #0) > 1) you have to use message: prefix Request for full-text search is https://code.google.com/p/gerrit/issues/detail?id=866 > 2) it only searches from open commits by default > 3) doing message:foo is:merged takes forever And https://code.google.com/p/gerrit/issues/detail?id=1441 is "Optimize commit message search predicate"
(In reply to comment #2) > (In reply to comment #0) > > 1) you have to use message: prefix > > Request for full-text search is > https://code.google.com/p/gerrit/issues/detail?id=866 > > > 2) it only searches from open commits by default > > 3) doing message:foo is:merged takes forever > > And https://code.google.com/p/gerrit/issues/detail?id=1441 is "Optimize > commit > message search predicate" No movement in either. Does gitblit make this report obsolete? It doesn't have fulltext search, but commit messages are indexed.
https://code.google.com/p/gerrit/issues/detail?id=866 was released with 2.8.
