Re: Can I use app specific document id as the document id that Solr uses for internal purposes?

2013-10-06 Thread Ertio Lew
eric string good enough for your app? > > > -- Jack Krupansky > > -Original Message- From: Ertio Lew > Sent: Sunday, October 06, 2013 1:36 PM > To: solr-user@lucene.apache.org > Subject: Re: Can I use app specific document id as the document id that > Solr uses for inter

Re: Can I use app specific document id as the document id that Solr uses for internal purposes?

2013-10-06 Thread Ertio Lew
n your Solr unique key field. > > -- Jack Krupansky > > -Original Message- From: Ertio Lew > Sent: Sunday, October 06, 2013 4:46 AM > To: solr-user@lucene.apache.org > Subject: Can I use app specific document id as the document id that Solr > uses for internal purpos

Re: Can I use app specific document id as the document id that Solr uses for internal purposes?

2013-10-06 Thread Ertio Lew
@Gora: >One wants to index "just >enough" data in the search engine. Plus, if one wants to do relevant >searches in large text blobs, documents, etc., those should be in the >search engine: Databases are bad at such searches. Perhaps you took me wrong.. :) may be I couldn't make that clear. I am

Re: Does the queryResultCache, contain all the results returned by main query or after filtering out

2013-10-06 Thread Ertio Lew
s? > > But to answer, no. The queryResultCache contains the top N > ids for the query. You control N by setting > in solrconfig.xml. It's often set to 2x the usual "rows" parameter > on the theory that people rarely page past the second page. > > Best, >

Re: Can I use app specific document id as the document id that Solr uses for internal purposes?

2013-10-06 Thread Ertio Lew
I meant that solr should not be thinking that it has to retrieve any thing further (as in any stored document data) after once it gets the doc id, so that one further look up for doc data is prevented. On Sun, Oct 6, 2013 at 2:49 PM, Ertio Lew wrote: > yeah I already configured it as a uni

Does the queryResultCache, contain all the results returned by main query or after filtering out

2013-10-06 Thread Ertio Lew
Does the queryResultCache, contain all the results returned by main query(q param) or it contains results prepared after all filter queries ?

Re: Can I use app specific document id as the document id that Solr uses for internal purposes?

2013-10-06 Thread Ertio Lew
t; On 6 October 2013 14:16, Ertio Lew wrote: > > Could I just use my application specific document id as the document id > > that solr uses for internal purposes, > [...] > > If this is a unique identifier, yes, you should be able to > do that. > > Regards, > Gora >

Can I use app specific document id as the document id that Solr uses for internal purposes?

2013-10-06 Thread Ertio Lew
Could I just use my application specific document id as the document id that solr uses for internal purposes, ie. indexing etc because I don't store any other field other than id of the document(rest document data is stored in DB). In my schema the only thing that I store is the document id, this

Re: Are indexes for different fields in a schema maintained separately ?

2013-10-06 Thread Ertio Lew
sorry this question got posted twice. I wasn't aware. On Sun, Oct 6, 2013 at 11:37 AM, Ertio Lew wrote: > Are indexes for different fields maintained separately, I mean if I have > two text fields both indexed separately within a schema, each of them would > have its own set

Are indexes for different fields in a schema maintained separately ?

2013-10-05 Thread Ertio Lew
Are indexes for different fields maintained separately, I mean if I have two text fields both indexed separately within a schema, each of them would have its own set of indexes, so that if I one field's index is quite bigger it doesn't affect anyhow another unless I use both of the fields together

Are indexes for different fields within a schema maintained separately ?

2013-10-05 Thread Ertio Lew
Are indexes for different fields maintained separately, I mean if I have two text fields both indexed separately within a schema, each of them would have its own set of indexes, so that if I one field's index is quite bigger it doesn't affect anyhow another unless I use both of the fields in one qu