This is not recommended, the recommended approach is a keyword field (using subfield or with an explicit side field with the different mapping).

True, but it's the only solution right now when analysis is required, since they decided to leave filtering support on keywords for 5.1. And if we want to do it the proper way later, we'll have to introduce a specific dialect just for 5.0...