Version: unspecified
Severity: normal
URL: http://code.google.com/p/gerrit/issues/detail?id=1441
See Also:
http://code.google.com/p/gerrit/issues/detail?id=866
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • demon | T38467 Impossible to search a commit from Gerrit | |||
| Resolved | • demon | T63463 Gerrit search: enable secondary index to allow latest operators | |||
| Resolved | • demon | T70271 Upgrade gerrit to 2.12 | |||
| Declined | Bawolff | T106666 Consider changing gerrit default change screen to CHANGE_SCREEN2 | |||
| Resolved | jcrespo | T139755 Need snapshot of 'reviewdb' on spare machine to test gerrit schema upgrades | |||
| Resolved | • demon | T131903 Update gerrit sshkey in role::ci::slave::labs when upgrade to Jessie happens | |||
| Resolved | Dzahn | T125018 replace gerrit server (ytterbium) with jessie server (lead) | |||
| Resolved | RobH | T123132 Need spare server to upgrade/migrate gerrit | |||
| Resolved | • Cmjohnson | T123531 check for memory upgrade for lead | |||
| Resolved | • demon | T126794 setup/deploy server lead as jessie gerrit server | |||
| Resolved | • Cmjohnson | T141415 decom ytterbium (datacenter) |
(In reply to comment #0)
- 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)
- you have to use message: prefix
Request for full-text search is https://code.google.com/p/gerrit/issues/detail?id=866
- it only searches from open commits by default
- 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)
- you have to use message: prefix
Request for full-text search is
https://code.google.com/p/gerrit/issues/detail?id=866
- it only searches from open commits by default
- 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.