Re: Issue with Join

Can a committer take a look at this please? On Wed, Dec 30, 2015 at 4:35 PM, William Bell wrote: > Yeah I ran it. It appears to only have an issue if the field for the core > on the outside is MultiValue, and the inside field is single value, and the > order of the field

Re: Issue with Join

Yeah I ran it. It appears to only have an issue if the field for the core on the outside is MultiValue, and the inside field is single value, and the order of the field has the code not as the first entry. Like: practicing_specialties_codes: > [ > - "PS1010", > -

Re: Issue with Join

Hello, Have you considered to pass NOT {!join from=prac_spec_code to=practicing_specialties_codes fromIndex=autosuggest}*:* as a q and look at debug output. Also there was a trick for dealing with pure negative queries q=*:* -foo:bar though it might be obsolete. On Tue, Dec 29, 2015 at

Re: Issue with Join

Thoughts? I can duplicate it at will... On Mon, Dec 28, 2015 at 9:02 PM, William Bell wrote: > I have having issues with {!join}. If the core have multiValued field and > the inner join does not have a multiValued field it does not find the > ones... > > Solr 5.3.1...

Issue with Join

I have having issues with {!join}. If the core have multiValued field and the inner join does not have a multiValued field it does not find the ones... Solr 5.3.1... 5.3.1 Example. PS1226 is in practicing_specialties_codes in providersearch core. This field is multiValued. in the autosuggest