For what it's worth, I have recently used the cross collection join. I did
make sure that the 2 fields were defined the same, as far as both being
'multi-value'. Although, I am not certain that is a requirement.
Now, the other thing I ran into is that my 'documents' collection was
sharded, say across 5 shards. But, my 'person' collection was on a single
shard. I came to realize that the only time the join was working was for
the 'documents' collection documents, that were on the same shard as the
'person' collection. My 'person' collection was quite small. So, to
address this, I simply replicated my 'person' collection across all 5
shards.
I'm still in the process of 'certifying' if what I described is
actually behaving the way I think it should. So far, so good.
Ron Haines
On Thu, Apr 27, 2023 at 9:53 AM Sergio García Maroto <marot...@gmail.com>
wrote:
> Hi,
>
> I am trying to use crossCollection join to be able to use sharding.
> I am joining to collections Person and documents. Finding people with
> documetns of type pdf. Just realised no people comes back
> and noticed PersonID in document core is multivalue field.
>
> <field name="PersonID" type="string" indexed="true" stored="true"
> docValues=
> "true" multiValued="true" />
>
> My query looks like
> {!join method=crossCollection from=PersonID to=PersonID fromIndex=document
> v='type:(pdf)'}
>
> Is this feature not working on multivalue fields? Is there any other
> option?
>
> Regards
> Sergio Maroto
>
