[
https://issues.apache.org/jira/browse/LUCENE-8565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Itamar Syn-Hershko updated LUCENE-8565:
---------------------------------------
Description:
SimpleQueryString lacks support for the `field:` operator for creating queries
which operate on fields other than the default field. Seems like one can either
get the parsed query to operate on a single field, or on ALL defined fields (+
weights). No support for specifying `field:value` in the query.
It probably wasn't forgotten, but rather left out for simplicity, but since we
are using this QP implementation more and more (mostly through Elasticsearch)
we thought it would be useful to have it in.
Seems like this is not too hard to pull off and I'll be happy to contribute a
patch for it.
was:
SimpleQueryString lacks support for the `field:` operator for creating queries
which operate on fields other than the default field. Seems like one can either
get the parsed query to operate on a single field, or on ALL defined fields (+
weights). No support for specifying `field:value` in the query.
It probably wasn't forgotten, but rather left out for simplicity, but since we
are using this QP implementation more and more (mostly through Elasticsearch)
we thought it would be
Seems like this is not too hard to pull off and I'll be happy to contribute a
patch for it.
> SimpleQueryString to support field filtering (aka Add field:text operator)
> --------------------------------------------------------------------------
>
> Key: LUCENE-8565
> URL: https://issues.apache.org/jira/browse/LUCENE-8565
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/queryparser
> Reporter: Itamar Syn-Hershko
> Priority: Minor
>
> SimpleQueryString lacks support for the `field:` operator for creating
> queries which operate on fields other than the default field. Seems like one
> can either get the parsed query to operate on a single field, or on ALL
> defined fields (+ weights). No support for specifying `field:value` in the
> query.
> It probably wasn't forgotten, but rather left out for simplicity, but since
> we are using this QP implementation more and more (mostly through
> Elasticsearch) we thought it would be useful to have it in.
> Seems like this is not too hard to pull off and I'll be happy to contribute a
> patch for it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
