lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frank li <fudon...@gmail.com>
Subject Re: Config join parse in solrconfig.xml
Date Tue, 07 Apr 2015 21:43:06 GMT
Cool. It actually works after I removed those extra columns. Thanks for
your help.

On Mon, Apr 6, 2015 at 8:19 PM, Erick Erickson <erickerickson@gmail.com>
wrote:

> df does not allow multiple fields, it stands for "default field", not
> "default fields". To get what you're looking for, you need to use
> edismax or explicitly create the multiple clauses.
>
> I'm not quite sure what the join parser is doing with the df
> parameter. So my first question is "what happens if you just use a
> single field for df?".
>
> Best,
> Erick
>
> On Mon, Apr 6, 2015 at 11:51 AM, Frank li <fudongli@gmail.com> wrote:
> > The error message was from the query with "debug=query".
> >
> > On Mon, Apr 6, 2015 at 11:49 AM, Frank li <fudongli@gmail.com> wrote:
> >
> >> Hi Erick,
> >>
> >>
> >> Thanks for your response.
> >>
> >> Here is the query I am sending:
> >>
> >>
> http://dev-solr:8080/solr/collection1/select?q={!join+from=litigation_id_ls+to=lit_id_lms}all_text:apple&fq=type:PartyLawyerLawfirm&facet=true&facet.field=lawyer_id_lms&facet.mincount=1&rows=0
> >> <
> http://dev-solr:8080/solr/collection1/select?q=%7B!join+from=litigation_id_ls+to=lit_id_lms%7Dall_text:apple&fq=type:PartyLawyerLawfirm&facet=true&facet.field=lawyer_id_lms&facet.mincount=1&rows=0
> >
> >>
> >> You can see it has "all_text:apple". I added field name "all_text",
> >> because it gives error without it.
> >>
> >> Errors:
> >>
> >> <lst name="error"><str name="msg">undefined field all_text number
party
> >> name all_code ent_name</str><int name="code">400</int></lst>
> >>
> >>
> >> These fields are defined as the default search fields in our
> >> solr_config.xml file:
> >>
> >> <str name="df">all_text number party name all_code ent_name</str>
> >>
> >>
> >> Thanks,
> >>
> >> Fudong
> >>
> >> On Fri, Apr 3, 2015 at 1:31 PM, Erick Erickson <erickerickson@gmail.com
> >
> >> wrote:
> >>
> >>> You have to show us several more things:
> >>>
> >>> 1> what exactly does the query look like?
> >>> 2> what do you expect?
> >>> 3> output when you specify &debug=query
> >>> 4> anything else that would help. You might review:
> >>>
> >>> http://wiki.apache.org/solr/UsingMailingLists
> >>>
> >>> Best,
> >>> Erick
> >>>
> >>> On Fri, Apr 3, 2015 at 10:58 AM, Frank li <fudongli@gmail.com> wrote:
> >>> > Hi,
> >>> >
> >>> > I am starting using join parser with our solr. We have some default
> >>> fields.
> >>> > They are defined in solrconfig.xml:
> >>> >
> >>> >       <lst name="defaults">
> >>> >        <str name="defType">edismax</str>
> >>> >        <str name="echoParams">explicit</str>
> >>> >        <int name="rows">10</int>
> >>> >        <str name="df">all_text number party name all_code
> ent_name</str>
> >>> >        <str name="qf">all_text number^3 name^5 party^3 all_code^2
> >>> > ent_name^7</str>
> >>> >        <str name="fl">id description market_sector_type parent
> >>> ult_parent
> >>> > ent_name title patent_title *_ls *_lms *_is *_texts *_ac *_as *_s
> *_ss
> >>> *_ds
> >>> > *_sms *_ss *_bs</str>
> >>> >        <str name="q.op">AND</str>
> >>> >      </lst>
> >>> >
> >>> >
> >>> > I found out once I use join parser, it does not recognize the default
> >>> > fields any more. How do I modify the configuration for this?
> >>> >
> >>> > Thanks,
> >>> >
> >>> > Fred
> >>>
> >>
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message