lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mikhail Khludnev <mkhlud...@griddynamics.com>
Subject Re: Specifying multiple query parsers
Date Wed, 29 Jul 2015 19:47:13 GMT
BlockJoinParentQParser does nothing specific just calls subroutine. The
question about redundant is _query_ is worthy per se, and here is the
answer: https://issues.apache.org/jira/browse/SOLR-4093
Note: spaces in subquery may lead to mistakes I'd rather recommend to use
{!.. v=$childq}&childq=... hack

On Wed, Jul 29, 2015 at 10:41 PM, Jamie Johnson <jej2003@gmail.com> wrote:

> Sorry answered my own question.  For those that are interested this is
> related to how BlockJoinParentQParser handles sub queries and looks like
> it's working as it should.
>
> On Wed, Jul 29, 2015 at 3:31 PM, Jamie Johnson <jej2003@gmail.com> wrote:
>
> > I have a use case where I want to use the block join query parser for the
> > top level query and for the nested portion a custom query parser.  I was
> > originally doing this, which worked
> >
> > {!parent which='type:parent'}_query_:{!myqp df='child_pay' v='"value
> foo"'}
> >
> > but switched to this which also worked
> >
> > {!parent which='type:parent'}{!myqp}child_pay:"value foo"
> >
> > I have never seen this type of syntax where you can specify multiple
> query
> > parsers inline, is this supposed to work or am I taking advantage of some
> > oversight in the local params implementation?
> >
>



-- 
Sincerely yours
Mikhail Khludnev
Principal Engineer,
Grid Dynamics

<http://www.griddynamics.com>
<mkhludnev@griddynamics.com>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message