@kismilan Did a quick glance over the Sphinx MySQL driver part, did not immediately find any related changes there => must be happening in Coreseek patches which I'm not really familiar with...
@kismilan Sphinx never did field truncation, must be Coreseek specfic. Also 2.0.2 is ancient, dated 2011. For segmentation, Sphinx has built-in "ngram_chars" that lets you index unigrams, and can also support the commercial Rosetta library.
@kismilan No, Sphinx does not do any truncation, we index everything that the database driver gives us. Can you make a test dataset (.sql + .conf + your test query) and email that to me?
@TitPetric Yes, all these are correct. Doing more licensing to fund the project better is, of course, one of the reasons. The fact there is *already* a bit of code in 3.x that I plan to move out to a paid version is another one.
@TitPetric RE2 is now always-on. New custom stemmers I can also integrate. However if the root cause here is IT security, I'm afraid right now (ie. before I manage to re-open) the only way would be to become a commercial customer and get a source level license.
@TitPetric Re delayed FOSS, several reasons there, basically "pure" open source model is not working, so changes are needed to keep Sphinx going. No clear "re-open date", maybe later in the year. Why, by the way? Most people never hack the scary C++ engine.