You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Matteo Grolla <ma...@gmail.com> on 2015/05/18 16:26:32 UTC

please confirm: pseudo join queries can only be performed on fields of exactly the same type

Hi,
	I tried performing a join query 
	{!join from=fA to=fB}
	where fA was string and fB was text  using keywordTokenizer

	it doesn't work, but it does if either fields are both string or both text.
	
	If you confirm this is the correct behavior I'll update the wiki

thanks


Re: please confirm: pseudo join queries can only be performed on fields of exactly the same type

Posted by Matteo Grolla <ma...@gmail.com>.
Thanks for the quick and precise answer,
	fb are lowercased so indexed tokens don't match
	
Il giorno 18/mag/2015, alle ore 16:54, Yonik Seeley ha scritto:

> They should not have to be *exactly* the same type... just compatible
> types such that the indexed tokens match.
> When you used the keywordTokenizer, was there other analysis such as
> lowercasing going on?
> 
> -Yonik
> 
> 
> On Mon, May 18, 2015 at 10:26 AM, Matteo Grolla <ma...@gmail.com> wrote:
>> Hi,
>>        I tried performing a join query
>>        {!join from=fA to=fB}
>>        where fA was string and fB was text  using keywordTokenizer
>> 
>>        it doesn't work, but it does if either fields are both string or both text.
>> 
>>        If you confirm this is the correct behavior I'll update the wiki
>> 
>> thanks
>> 


Re: please confirm: pseudo join queries can only be performed on fields of exactly the same type

Posted by Yonik Seeley <ys...@gmail.com>.
They should not have to be *exactly* the same type... just compatible
types such that the indexed tokens match.
When you used the keywordTokenizer, was there other analysis such as
lowercasing going on?

-Yonik


On Mon, May 18, 2015 at 10:26 AM, Matteo Grolla <ma...@gmail.com> wrote:
> Hi,
>         I tried performing a join query
>         {!join from=fA to=fB}
>         where fA was string and fB was text  using keywordTokenizer
>
>         it doesn't work, but it does if either fields are both string or both text.
>
>         If you confirm this is the correct behavior I'll update the wiki
>
> thanks
>