Hi lig, thanks for the feedback and the offer to help as well,
Personally, I use search almost daily and it works well for me. Maybe I'm biased having been involved with the design though. E.g. if you want to find part of a word, like hair you can type hair* to find haircut and hairy.
Some of what you're describing might be just usability improvements to add perhaps?
Our current plan is to focus on full text search in MySQL and Postgres for Team Edition,
- Install needs to remain simple, and get even more simple
- We're making good progress on full text search, including support for CJK
We'd love to have more help here if you're interested?
Lucene and Elastic search would be good for Enterprise Edition I think, since their setups are complicated and the benefit of that investment doesn't really pay off until we're into enterprise scenarios.
I don't think we should give up on keeping deployment simple and improving on search in the database--even if that means reaching out to MySQL and Postgres with specific requests for what we need in their future versions...