which field type are you specifying in your schema.xml for the fields that you search upon? if you are using "text" then this causes your input text to be stemmed to a common root making your searches more flexible. For instance: if you have the term "dreaming" in one row/document and the term "dream" in another, then this could be stemmed to "dreami" or something like during indexing. This effectively causes both your documents to match when you search for "dream" in Solr but you would only return 1 result if you searched directly in your database.
On 3 February 2011 22:37, Geert-Jan Brits <gbr...@gmail.com> wrote: > Make sure your index is completely commited. > > curl 'http://localhost:8983/solr/update?commit=true' > > > http://wiki.apache.org/solr/UpdateXmlMessages#A.22commit.22_and_.22optimize.22 > > for an overview: > http://lucene.apache.org/solr/tutorial.html > > hth, > Geert-Jan > <http://techgurulive.com/2010/11/22/apache-solr-commit-and-optimize/> > > 2011/2/3 Esclusa, Will <william.escl...@bonton.com> > > > Both the application and the SOLR gui match (with the incorrect number > > of course :-) ) > > > > At first I thought it could be a schema problem, but we went though it > > with a fine comb and compared it to the one in our stage environment. > > What is really weird is that I grabbed one of the product ID that are > > not showing up in SOLR from the DB, search through the SOLR GUI and it > > found it. > > > > -----Original Message----- > > From: Savvas-Andreas Moysidis > > [mailto:savvas.andreas.moysi...@googlemail.com] > > Sent: Thursday, February 03, 2011 4:57 PM > > To: solr-user@lucene.apache.org > > Subject: Re: Index Not Matching > > > > that's odd..are you viewing the results through your application or the > > admin console? if you aren't, I'd suggest you use the admin console just > > to > > eliminate the possibility of an application bug. > > We had a similar problem in the past and turned out to be a mixup of our > > dev/test instances.. > > > > On 3 February 2011 21:41, Esclusa, Will <william.escl...@bonton.com> > > wrote: > > > > > Hello Saavs, > > > > > > I am 100% sure we are not updating the DB after we index the data. We > > > are specifying the same fields on both queries. Our prod boxes do not > > > have access to QA or DEV, so I would expect a connection error when > > > indexing if this is the case. No connection errors in the logs. > > > > > > > > > > > > -----Original Message----- > > > From: Savvas-Andreas Moysidis > > > [mailto:savvas.andreas.moysi...@googlemail.com] > > > Sent: Thursday, February 03, 2011 4:26 PM > > > To: solr-user@lucene.apache.org > > > Subject: Re: Index Not Matching > > > > > > Hello, > > > > > > Are you definitely positive your database isn't updated after you > > index > > > your > > > data? Are you querying against the same field(s) specifying the same > > > criteria both in Solr and in the database? > > > Any chance you might be pointing to a dev/test instance of Solr ? > > > > > > Regards, > > > - Savvas > > > > > > On 3 February 2011 20:17, Esclusa, Will <william.escl...@bonton.com> > > > wrote: > > > > > > > Greetings! > > > > > > > > > > > > > > > > My organization is new to SOLR, so please bare with me. At times, > > we > > > > experience an out of sync condition between SOLR index files and our > > > > Database. We resolved that by clearing the index file and performing > > a > > > full > > > > crawl of the database. Last time we noticed an out of sync > > condition, > > > we > > > > went through our procedure of deleting and crawling, but this time > > it > > > did > > > > not fix it. > > > > > > > > > > > > > > > > For example, search for swim on the DB and we get 440 products, but > > > yet > > > > SOLR states we have 214 products. Has anyone experience anything > > like > > > this? > > > > Does anyone have any suggestions on a trace we can turn on? Again, > > we > > > are > > > > new to SOLR so any help you can provide is greatly appreciated. > > > > > > > > > > > > > > > > Thanks! > > > > > > > > > > > > > > > > Will > > > > > > > > > > > > > > > > > > > > > >
