| • chasemp | |
| Feb 11 2015, 6:44 PM |
| F39385: Screen_Shot_2015-02-11_at_12.38.50_PM.png | |
| Feb 11 2015, 6:44 PM |
| F39387: Screen_Shot_2015-02-11_at_12.39.23_PM.png | |
| Feb 11 2015, 6:44 PM |
| F39383: Screen_Shot_2015-02-11_at_12.38.38_PM.png | |
| Feb 11 2015, 6:44 PM |
| F39389: Screen_Shot_2015-02-11_at_12.40.05_PM.png | |
| Feb 11 2015, 6:44 PM |
We switched over to MySQL for our search backend today. A few issues are now flagged (this doesn't necessarily mean we need to change them) but it's more like a "are you sure this is what you want?" message from the setup check. I'm wondering if 'stop words' we leave default, change the min_word_len to 3 and change default boolean search to AND.
@Springle thoughts? :)
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • mmodell | T146789 Phab Advanced Search no longer showing typical results | |||
| Resolved | jcrespo | T146673 Contention on search phabricator database creating full phabricator outages | |||
| Resolved | • mmodell | T146843 Re-evaluate how we implement phabricator's search engine | |||
| Resolved | None | T89369 Insufficient error message when search character limit is hit | |||
| Resolved | • chasemp | T89274 Mysql search issues flagged by Phabricator setup |
+1 to all three options, imo.
The ARIA engine uses the same fulltext stopword list as MyISAM did, which is fairly long[1]. We also need to increase the aria_pagecache_buffer_size.
[1] https://mariadb.com/kb/en/mariadb/stopwords/#myisam-stopwords
+1 to the word length (I just reported this, see T89369) and +1 to the operator. To be honest I would classify the fact that a search engine defaults to OR as a bug nowadays.
Question: Is the fact that the search ignores my attempts to type AND a bug I should report?
Change 190775 had a related patch set uploaded (by Springle):
phabricator using mysql fulltext T89274, tweaked for mariadb/aria
The ft_boolean_syntax fix for default AND behavior has been applied as it doesn't technically need a DB restart. The ft_min_word_len, stopwords, and table rebuild do need the restart.
The technical reason is that MySQL boolean fulltext syntax[1] uses + instead of AND. A phabricator bug report pitching it as a user interface fail might be justified.
http://dev.mysql.com/doc/refman/5.5/en/fulltext-boolean.html
@Springle I think the puppet looks good. When is good for you to knock this out? I'll try to sync up with you on irc also. Thanks again
Change 190775 merged by Springle:
phabricator using mysql fulltext T89274, tweaked for mariadb/aria