Comment 23 for bug 1152863

I don't think anyone is suggesting deep changes to Evergreen internals. As Mike points out, the query parser code was already designed with configurable operators in mind. I agree that it makes the most sense to tap into this potential rather than try a wrapper-style approach.

It's entirely possible that these configuration options will need some troubleshooting and bugfixes to make work; they have been (as far as I know) sitting unused for quite some time. If one were to run into issues going this route, I think many here would be happy to help work out the kinks.