[
https://issues.apache.org/jira/browse/SOLR-14597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17150438#comment-17150438
]
Gus Heck commented on SOLR-14597:
---------------------------------
This thought has occurred to me, but the coordination of several parts across
both Lucene and Solr layers seems awkward for a packge/plugin (Solr parser, a
couple new Lucene filters, etc), and I do hope that it is a generally useful
parser as you mention. When we sort out the legalities and get a patch up this
will become more clear, but generally it adds another javacc based parser, that
was based on and is able to reuse some bits of the standard parser (a few of
which needed to be extracted/or made accessible). There are also a few small
tweaks to core classes, (which seem justified to me, but of course review and
commentary is welcome). So even if a package/plugin is part of the final result
we will likely have some changes to Solr & Lucene directly as well.
> Advanced Query Parser
> ---------------------
>
> Key: SOLR-14597
> URL: https://issues.apache.org/jira/browse/SOLR-14597
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: query parsers
> Affects Versions: 8.6
> Reporter: Mike Nibeck
> Assignee: Gus Heck
> Priority: Major
>
> This JIRA ticket tracks the progress of SIP-9, the Advanced Query Parser that
> is being donated by the Library of Congress. Full description of the feature
> can be found on the SIP Page.
> [https://cwiki.apache.org/confluence/display/SOLR/SIP-9+Advanced+Query+Parser]
> Briefly, this parser provides a comprehensive syntax for users that use
> search on a daily basis. It also reserves a smaller set of punctuators than
> other parsers. This facilitates easier handling of acronyms and punctuated
> patterns with meaning ( such as C++ or 401(k) ). The new syntax opens up some
> advanced features while also preventing access to arbitrary features via
> local parameters. This parser will be safe for accepting user queries
> directly with minimal pre-parsing, but for use cases beyond it's established
> features alternate query paths (using other parsers) will need to be supplied.
> The code drop is being prepared and will be supplied as soon as we receive
> guidance from the PMC regarding the proper process. Given that the Library
> already has a signed CCLA we need to understand which of these (or other
> processes) apply:
> [http://incubator.apache.org/ip-clearance/ip-clearance-template.html]
> and
> [https://www.apache.org/licenses/contributor-agreements.html#grants]
--
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
