You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking for a Lucene parser/builder and first found https://github.com/bripkens/lucene, I quickly noticed it was basically dead and unmaintained. The open issues highlight critical problems that are claimed to be solved in liqe. The big down side for me is that I need a parser/builder that supports all (if not, as many as possible) Lucene features, and I can't afford to go without fuzzy searches, proximity searches and boosting terms.
I would like to know if supporting those features is planned. I understand that liqe is not just a parser/builder and implementing those features in the search engine is complicated, I assume it's the reason why they are not supported at the moment.
If supporting those features is too complicated to implement in the search engine, is it possible to add partial support (so just for the parser and the builder)?
The text was updated successfully, but these errors were encountered:
Hi,
I was looking for a Lucene parser/builder and first found https://github.com/bripkens/lucene, I quickly noticed it was basically dead and unmaintained. The open issues highlight critical problems that are claimed to be solved in liqe. The big down side for me is that I need a parser/builder that supports all (if not, as many as possible) Lucene features, and I can't afford to go without fuzzy searches, proximity searches and boosting terms.
I would like to know if supporting those features is planned. I understand that liqe is not just a parser/builder and implementing those features in the search engine is complicated, I assume it's the reason why they are not supported at the moment.
If supporting those features is too complicated to implement in the search engine, is it possible to add partial support (so just for the parser and the builder)?
The text was updated successfully, but these errors were encountered: