[child] has childFilter param. Also, mind about [subquery]
On Wed, Jun 6, 2018 at 9:33 AM, Ryan Yacyshyn
wrote:
> Hi all,
>
> I'm looking for a way to query nested documents that would return the
> parent documents along with its child documents nested under it, but only
> the child documents th
Thanks Man.
On Mon, 14 Dec 2015 at 12:19 Mikhail Khludnev
wrote:
> In addition to the link in the previous response,
> http://blog.griddynamics.com/2013/09/solr-block-join-support.html provides
> an example of such combination. From my experience fq doen't participate in
> highlighting nor scori
In addition to the link in the previous response,
http://blog.griddynamics.com/2013/09/solr-block-join-support.html provides
an example of such combination. From my experience fq doen't participate in
highlighting nor scoring.
On Mon, Dec 14, 2015 at 2:45 PM, Novin Novin wrote:
> Hi Mikhail,
>
>
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
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
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={!
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
On Thu, May 14, 2015 at 12:01 AM, Tom Devel wrote:
> I tried to repost the whole modified document (the parent and ALL of its
> children as one file), and it seems to work on a small toy example, but of
> course I cannot be sure for a larger instance with thousands of documents,
> and I would lik
Sankalp,
would you mind to post debugQuery=on output, without it it's hard to get
what's the problem?
However, it's worth to mention that Andrey's suggestion seems really
promising.
On Tue, Feb 17, 2015 at 8:19 PM, Sankalp Gupta
wrote:
> Hi Mikhail,
>
> It won't solve my problem.
> For ex:
> S
How about find all parents which have at least one child with address:city1
and then "not"
Like (not sure about syntax at all)
q=-{!parent which=userid:*}address:city1
17.02.2015, 20:21, "Sankalp Gupta" :
> Hi Mikhail,
>
> It won't solve my problem.
> For ex:
> Suppose my docs are like this:
>
Hi Mikhail,
It won't solve my problem.
For ex:
Suppose my docs are like this:
city1
city2
city2
city3
Now if I want* a query to return me all the users not having any address*
related to *city1* (i.e. only userid=2 should be in the result)a
try to search all children remove those who has a value1 by dash, then join
remaining
q={!parent which=contentType:parent}contentType:child -contentType:value1
if the space in underneath query causes the problem try to escape it or
wrap to v=$subq
On Tue, Feb 17, 2015 at 4:13 PM, Sankalp Gupta
11 matches
Mail list logo
