Hi Alex,
Below is where my schema is stored:-
/opt/solr/solr/collection1/conf#
File name: schema.xml
Below output for body
<fields>
<field name="id" type="string" indexed="true" stored="true"
required="true" />
<field name="uid" type="slong" indexed="true" stored="true"
required="true" />
<field name="box" type="string" indexed="true" stored="true"
required="true" />
<field name="user" type="string" indexed="true" stored="true"
required="true" />
<field name="hdr" type="text" indexed="true" stored="false" />
<field name="body" type="text" indexed="true" stored="false" />
<field name="from" type="text" indexed="true" stored="false" />
<field name="to" type="text" indexed="true" stored="false" />
<field name="cc" type="text" indexed="true" stored="false" />
<field name="bcc" type="text" indexed="true" stored="false" />
<field name="subject" type="text" indexed="true" stored="false" />
</fields>
Anything you see that I should be concerned about?
On Wed, Feb 25, 2015 at 1:27 AM, Kevin Laurie <superinterstel...@gmail.com>
wrote:
> Hi Alex,
> Sorry for such noobness question.
> But where does the schema file go in Solr? Is the directory below correct?
> /opt/solr/solr/collection1/data
> Correct?
> Thanks
> Kevin
>
> On Wed, Feb 25, 2015 at 1:21 AM, Kevin Laurie
> <superinterstel...@gmail.com> wrote:
> > Dear Alex,
> > I checked the log. When searching the fields From , To, Subject. It
> records
> > it
> > When searching Body, there is no log showing. I am assuming it is a
> problem
> > in the schema.
> >
> > Will post schema.xml output in next mail.
> >
> > On Wed, Feb 25, 2015 at 1:09 AM, Alexandre Rafalovitch <
> arafa...@gmail.com>
> > wrote:
> >>
> >> Look for the line like this in your log with the search matching the
> >> body. Maybe put a nonsense string and look for that. This should tell
> >> you what the Solr-side search looks like.
> >>
> >> The thing that worries me here is: rows=107178 - that's most probably
> >> what's blowing up Solr. You should be paging, not getting everything.
> >> And that number being like that, it may mean your client makes two
> >> requests, once to get the result count and once to get the rows
> >> themselves. It's the second request that is most probably blowing up.
> >>
> >> Once you get the request, you should be able to tell what fields are
> >> being searched and check those fields in schema.xml for field type and
> >> then field type's definition. Which is what I asked for in the
> >> previous email.
> >>
> >> Regards,
> >> Alex.
> >>
> >> On 24 February 2015 at 11:55, Kevin Laurie <superinterstel...@gmail.com
> >
> >> wrote:
> >> > 155092 [qtp433527567-13] INFO org.apache.solr.core.SolrCore ?
> >> > [collection1] webapp=/solr path=/select
> >> >
> >> >
> params={sort=uid+asc&fl=uid,score&q=subject:"price"&fq=%2Bbox:ac553604f7314b54e62300003555fc1a+%2Buser:"
> u...@domain.net"&rows=107178}
> >> > hits=1237 status=0 QTime=1918
> >>
> >>
> >>
> >> ----
> >> Solr Analyzers, Tokenizers, Filters, URPs and even a newsletter:
> >> http://www.solr-start.com/
> >
> >
>
