[
https://issues.apache.org/jira/browse/LUCENE-9528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199871#comment-17199871
]
Dawid Weiss commented on LUCENE-9528:
-------------------------------------
I think this query parser is great, really! It does have some things that could
be cleaned up but it is the only query parser that is externally extensible and
usable for me. It supports multifield expansion for unqualified terms and it is
*very* flexible - the parse tree resulting from query parsing can be adjusted
and enhanced in multiple ways without touching the parser code (you only touch
the post processing tree pipeline and/or the builders).
We have been using it with success in both our in-house projects (Lingo4G) and
in combination with Solr. I don't see the reason to remove it. In fact, I think
the approach this query parser takes (intermediate representation) is much
superior to the "classic" query parser which creates intermediate Query
instances right away. And the span query parser... eh. This isn't usable at all
- the syntax is too strange - it was difficult to use even for me as a
developer.
> Clean up obsolete and commented-out cruft from StandardSyntaxParser.jj
> ----------------------------------------------------------------------
>
> Key: LUCENE-9528
> URL: https://issues.apache.org/jira/browse/LUCENE-9528
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Minor
> Fix For: master (9.0)
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The indentation in that file is crazy. So are micro-optimizations which make
> reading the syntax parser much more difficult than it actually is.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
