re-index from scratch. Solr won't retroactively remove duplicate
>> > >> entries.
>> > >>
>> > >> > On the stats admin/stats page you should see maxDocs and numDocs.
>> The
>> > >> difference
>> > >> between these sh
unique keys. All that happens is Solr will
> > replace
> > >> any
> > >> pre-existing documents where *you've* defined the when a
> > >> new doc is added...
> > >>
> > >> Hope this helps
> > >
ce
>> >> any
>> >> pre-existing documents where *you've* defined the when a
>> >> new doc is added...
>> >>
>> >> Hope this helps
>> >> Erick
>> >>
>> >> On Thu, Jul 7, 2011 at 10:16 AM, Mark juszczec &
>
> >> > No, I don't. Let me look into that and post my results.
> >> >
> >> > Mark
> >> >
> >> >
> >> > On Thu, Jul 7, 2011 at 10:14 AM, Bob Sandiford <
> >> bob.sandif...@sirsidynix.com
> >> >> w
n Thu, Jul 7, 2011 at 10:14 AM, Bob Sandiford <
>> bob.sandif...@sirsidynix.com
>> >> wrote:
>> >
>> >> Hi, Mark.
>> >>
>> >> I haven't used DIH myself - so I'll need to leave comments on your set
>> up
>> >> to others
fter each
> delta),
> >> do you run a 'commit'? Do you run an 'optimize'? (Without the
> optimize,
> >> 'deleted' records still show up in query results...)
> >>
> >> Bob Sandiford | Lead Software Engineer | SirsiDynix
> &
Am 07.07.2011 16:52, schrieb Mark juszczec:
> Ok. That's really good to know because optimization of that kind will be
> important.
Optimization is only important if you had a lot of deletes or updated
docs, or if you want your segments get merged. (At least that's what I
know about it.)
>
> Wha
Ok. That's really good to know because optimization of that kind will be
important.
What of commit? Does it somehow remove the previous version of an updated
record?
On Thu, Jul 7, 2011 at 10:49 AM, Michael Kuhlmann wrote:
> Am 07.07.2011 16:14, schrieb Bob Sandiford:
> > [...] (Without the o
Software Engineer | SirsiDynix
>> P: 800.288.8020 X6943 | bob.sandif...@sirsidynix.com
>> www.sirsidynix.com
>>
>>
>> > -Original Message-
>> > From: Mark juszczec [mailto:mark.juszc...@gmail.com]
>> > Sent: Thursday, July 07, 2011 10:04 A
Am 07.07.2011 16:14, schrieb Bob Sandiford:
> [...] (Without the optimize, 'deleted' records still show up in query
> results...)
No, that's not true. The terms remain in the index, but the document
won't show up any more.
Optimize is only for performance (and disk space) optimization, as the
na
> P: 800.288.8020 X6943 | bob.sandif...@sirsidynix.com
> www.sirsidynix.com
>
>
> > -Original Message-
> > From: Mark juszczec [mailto:mark.juszc...@gmail.com]
> > Sent: Thursday, July 07, 2011 10:04 AM
> > To: solr-user@lucene.apache.org
> > Subject: Re:
Thursday, July 07, 2011 10:04 AM
> To: solr-user@lucene.apache.org
> Subject: Re: updating existing data in index vs inserting new data in
> index
>
> Bob
>
> Thanks very much for the reply!
>
> I am using a unique integer called order_id as the Solr index key.
>
> My
Bob
Thanks very much for the reply!
I am using a unique integer called order_id as the Solr index key.
My query, deltaQuery and deltaImportQuery are below:
The test I am running is two part:
1. After I do a full import of the index, I insert a brand new record (with
a never existed
What are you using as the unique id in your Solr index? It sounds like you may
have one value as your Solr index unique id, which bears no resemblance to a
unique[1] id derived from your data...
Or - another way to put it - what is it that makes these two records in your
Solr index 'the same',
14 matches
Mail list logo
