Re: Indexing question on individual field update

Thanks Eric and Shawn, appreciate your help. -- View this message in context: http://lucene.472066.n3.nabble.com/Indexing-question-on-individual-field-update-tp4116605p4116831.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Indexing question on individual field update

Update and add are basically the same thing if there's an existing document. There will be some performance consequence since you're getting the stored fields on the server as opposed to getting the full input from the external source and handing it to Solr. However, I know of at least one situatio

Re: Indexing question on individual field update

On 2/11/2014 2:37 PM, shamik wrote: Eric, Thanks for your reply. I should have given a better context. I'm currently running an incremental crawl daily on this particular source and indexing the documents. Incremental crawl looks for any change since last crawl date based on the document publ

Re: Indexing question on individual field update

Ok, I was wrong here. I can always set the indextimestamp field with current time (NOW) for every atomic update. On a similar note, is there any performance constraint with updates compared to add ? -- View this message in context: http://lucene.472066.n3.nabble.com/Indexing-question-on-individ

Re: Indexing question on individual field update

Eric, Thanks for your reply. I should have given a better context. I'm currently running an incremental crawl daily on this particular source and indexing the documents. Incremental crawl looks for any change since last crawl date based on the document publish date. But, there's no way for me to

Re: Indexing question on individual field update

I'm assuming you're using the atomic update feature to update the individual field, why not use it when you replace the rest of the doc? Best, Erick On Mon, Feb 10, 2014 at 5:20 PM, Shamik Bandopadhyay wrote: > Hi, > > I'm currently indexing a bunch of fields for a given document. For e.g. >

Re: Indexing question

you can do this with cores. You can have one core to serve the public, and one for indexing. Then, when you've finished updating your index, you use the core admin handler to swap the cores around. Then you do the same thing the following night. Doesn't require any file moving nor any restarts of s

Re: Indexing question

Hello, I do nightly builds for one of my sites. I build the new index in a parallel directory. When it is finished I move the old files to a backup directory(I only save one, delete the previous), move the new database files to the correct place, then stop and restart solr. It sees the new databas

Re: Indexing question

Hi Ron, If you turn off autoCommit and only commit after your delete and refresh, the user's experience will be totally uninterrupted. Commits are used to control visibility in a Solr index. Michael Della Bitta Appinions 18 East 41st Street, 2nd

Re: RE: Indexing Question for large dataset

for all your responses so far! > > -Original Message- > From: kenf_nc [mailto:ken.fos...@realestate.com] > Sent: Wednesday, April 13, 2011 1:15 PM > To: solr-user@lucene.apache.org > Subject: RE: Indexing Question for large dataset > > Is NAME a product name? W

RE: Indexing Question for large dataset

Message- From: kenf_nc [mailto:ken.fos...@realestate.com] Sent: Wednesday, April 13, 2011 1:15 PM To: solr-user@lucene.apache.org Subject: RE: Indexing Question for large dataset Is NAME a product name? Why would it be multivalue? And why would it appear on more than one document? Is each

RE: Indexing Question for large dataset

Is NAME a product name? Why would it be multivalue? And why would it appear on more than one document? Is each 'document' a package of products? And the pricing tiers are on the package, not individual pieces? So sounds like you could, potentially, have a PriceListX column for each user. As your

RE: Indexing Question for large dataset

r all those columns)? Example Query: q=name&fl=NAME,ID&facet=true&facet.field=PRICELIST500 Thanks, Josh B. -Original Message- From: kenf_nc [mailto:ken.fos...@realestate.com] Sent: Wednesday, April 13, 2011 10:47 AM To: solr-user@lucene.apache.org Subject: Re: Indexing Ques

Re: Indexing Question for large dataset

Indexing isn't a problem, it's just disk space and space is cheap. But, if you do facets on all those price columns, that gets put into RAM which isn't as cheap or plentiful. Your cache buffers may get overloaded a lot and performance will suffer. 2000 price columns seems like a lot, could the doc

Re: Indexing question - split word and comma

On Thu, 2007-07-05 at 11:56 -0700, Mike Klaas wrote: > On 5-Jul-07, at 11:43 AM, Martin Grotzke wrote: > > > Hi all, > > > > I have a document with a name field like this: > > MP3-Player, Apple, »iPod nano«, silber, > > 4GB > > > > and want to find "apple". Unfortunately, I only find "apple,"... >

Re: Indexing question - split word and comma

On 5-Jul-07, at 11:43 AM, Martin Grotzke wrote: Hi all, I have a document with a name field like this: MP3-Player, Apple, »iPod nano«, silber, 4GB and want to find "apple". Unfortunately, I only find "apple,"... Can anybody help me with this? Sure: you're using WhitespaceAnalyzer, which onl