Be careful with URL encoding... that may be messing you up depending
on how you are trying to submit the query (and the single & you were
using as AND)
fq={!join from=root_id to=id}type:arm AND attr1=left
fq={!join from=root_id to=id}type:leg AND attr1=right
-Yonik
http://lucidworks.com
On Wed,
Got puzzled now! If instead of AND I use &, it works:
fq = {!join from=root_id to=id}type:leg & {!join from=root_id to=id}type:arm
I am definitly missing something, I don't know what... Shouldn't both be
the same?
[]s
2013/7/10 Marcelo Elias Del Valle
> Dominique,
> I tried also:
> fq = {!jo
Dominique,
I tried also:
fq = {!join from=root_id to=id}type:leg AND {!join from=root_id
to=id}type:arm
If I understood what you said correctly, that should return something too,
right? It also got me 0 results...
2013/7/10 Dominique Debailleux
> Sorry, I didn't check preciselyI guess in yo
Sorry, I didn't check preciselyI guess in your sample &attr1 applies to
the body, not the legs, that could explain your problem
2013/7/10 Marcelo Elias Del Valle
> This
> fq = {!join from=root_id to=id}type:leg&attr1=right OR {!join from=root_id
> to=id}type:arm&attr1=left
> works even if I
This
fq = {!join from=root_id to=id}type:leg&attr1=right OR {!join from=root_id
to=id}type:arm&attr1=left
works even if I have attr1=left1 in the second condition. My goal is to
select bodies that matches both conditions.
It's strange, but if I try
fq = {!join from=root_id to=id}type:leg&attr1=rig
try fq = {!join from=root_id to=id}type:leg&attr1=right OR {!join
from=root_id to=id}type:arm&attr1=left
Dom
2013/7/10 Marcelo Elias Del Valle
> Hello,
>
> I am playing with joins here just to test what I can do with them. I
> have been learning a lot, but I am still having some troubles
Hello,
I am playing with joins here just to test what I can do with them. I
have been learning a lot, but I am still having some troubles with more
complex queries.
For example, suppose I have the following documents:
- id = 1 - name = Humblebee - age = 1000
- id = 2 - type = arm -
