Hi Mikhail,

I'm having a little bit problem to construct the query for solr when I have
been trying to use block join query. As you said, i can't use + or <space>
in front of block join query, so I have to put *{**!parent
which="doctype:200"}  *in front. and after this, all fields are child
document, so I can't add any parent document field, if I add parent doc
field it would give me nothing because field is not exist in child
document.

But I can still add parent doc in "fq". Does it going to be cause any
trouble something related to highlight or scoring, because I was using
parent doc field in q not in fq.

Thanks,
Novin

On 12 December 2015 at 00:01, Novin <toe.al...@gmail.com> wrote:

> No Worries, I was just wondering what did I miss.  And thanks for blog
> link.
>
>
> On 11/12/2015 18:52, Mikhail Khludnev wrote:
>
>> Novin,
>>
>> I regret so much. It's my pet peeve in Solr query parsing. Handling s
>> space
>> is dependent from the first symbol of query sting
>> This will work (starts from '{!' ):
>> q={!parent which="doctype:200"}flow:[624 TO 700]
>> These won't due to " ", "+":
>> q= {!parent which="doctype:200"}flow:[624 TO 700]
>> q=+{!parent which="doctype:200"}flow:[624 TO 700]
>> Subordinate clauses with spaces are better handled with "Nested Queries"
>> or
>> so, check the post
>> <
>> http://blog.griddynamics.com/2013/12/grandchildren-and-siblings-with-block.html
>> >
>>
>>
>> On Fri, Dec 11, 2015 at 6:31 PM, Novin <no...@temetra.com> wrote:
>>
>> Hi Guys,
>>>
>>> I'm trying  block join query, so I have tried   +{!parent
>>> which="doctype:200"}flow:624     worked fine. But when i tried +{!parent
>>> which="doctype:200"}flow:[624 TO 700]
>>>
>>> Got the below error
>>>
>>> org.apache.solr.search.SyntaxError: Cannot parse 'flow_l:[624':
>>> Encountered \"<EOF>\" at line 1, column 11.\nWas expecting one of:\n
>>> \"TO\" ...\n    <RANGE_QUOTED> ...\n <RANGE_GOOP> ...\n
>>>
>>> Just wondering too, can we able to do range in block join query.
>>>
>>> Thanks,
>>> Novin
>>>
>>>
>>>
>>>
>>>
>>>
>>
>

Reply via email to