Re: Specifying multiple query parsers

2015-07-29 Thread Mikhail Khludnev
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=...

Re: Specifying multiple query parsers

2015-07-29 Thread Jamie Johnson
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 wrote: > I have a use case where I want to use the block join query parser for

Specifying multiple query parsers

2015-07-29 Thread Jamie Johnson
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