: So, I think a lot of people may be missing that power. I suspect it's
I've added some comments to the relevant pages as reminders to go back and
add more detail later so we don't lose track of the doc feedback expressed
in this thread ... when i get more time i'll try to go back and fill that
:
>>>
>>> * Solr QParsers may now be directly invoked in the lucene query syntax
>>> via localParams and without the _query_ magic field hack.
>>> Example: foo AND {!term f=myfield v=$qq}
>>>
>>> -- Jack Krupansky
>>>
>>> -Orig
ery_ magic field hack.
>> Example: foo AND {!term f=myfield v=$qq}
>>
>> -- Jack Krupansky
>>
>> -Original Message----- From: Jack Krupansky
>> Sent: Thursday, July 10, 2014 12:14 AM
>>
>> To: solr-user@lucene.apache.org
>> Subject: Re:
ND {!term f=myfield v=$qq}
>
> -- Jack Krupansky
>
> -Original Message- From: Jack Krupansky
> Sent: Thursday, July 10, 2014 12:14 AM
>
> To: solr-user@lucene.apache.org
> Subject: Re: Complement of {!join}
>
> I think this is the Jira that implemented that feature:
>
10, 2014 12:14 AM
To: solr-user@lucene.apache.org
Subject: Re: Complement of {!join}
I think this is the Jira that implemented that feature:
SOLR-4093 - localParams syntax for standard query parser
https://issues.apache.org/jira/browse/SOLR-4093
Yeah, I don't think this is fully docum
Krupansky
-Original Message-
From: Alexandre Rafalovitch
Sent: Wednesday, July 9, 2014 9:10 PM
To: solr-user@lucene.apache.org
Subject: Re: Complement of {!join}
Ok, so cannot be eDisMax at the top.
However, the point I really am trying to make does not seem to be in
those links. All the exa
Ok, so cannot be eDisMax at the top.
However, the point I really am trying to make does not seem to be in
those links. All the examples of local parameters I have seen use them
at the start of the query as a standalone component. I haven't seen
examples where a query string contains several of the
:
: Somebody (with more knowledge) should write up an in-depth article on
: this issue and whether the parent parser has to be default (lucene) or
: whatever.
It's a feature of Solr's standard query parser...
https://cwiki.apache.org/confluence/display/solr/Query+Syntax+and+Parsing
https://cwiki
I think any sub-clause can use a local syntax and branch off into
different query parsers. I could not find any examples of it either
but really need to do an advanced search and came up with this:
{!switch case='*:*' default=$q_lastName v=$lastName}
AND {!switch case='*:*' default=$q_first
Thank you so much for the quick reply, Erik. And wow: I didn't realize you
could use join that fluidly. Very nice.
Is there some trove of Solr doc that I'm missing where this natural syntax
is explained? I wouldn't have asked such a basic question except that I
found no evidence that this was poss
Maybe something like q=*:* AND NOT {!join … } would do the trick? (it’ll
depend on your version of Solr for support of the {!…} more natural nested
queries)
Erik
On Jul 9, 2014, at 11:24 AM, Bruce Johnson wrote:
> === Short-version ===
> Is there a way to join on the complement of a
=== Short-version ===
Is there a way to join on the complement of a query? I want the only the
Solr documents for which the nested join query does not match.
=== Longer-version ===
Query-time joins with {!join} are great at modeling the SQL equivalent of
patterns like this:
SELECT book_name FROM
12 matches
Mail list logo