I was unclear. Our use case is that for some data sources we submit the
same thing over and over. Overwriting deletes the first one and we end up
with long commit times, and also we lose the earliest known date for the
document. We would like to have the second update attempt dropped. So we
would like to use "allowDups=false overwritePending=false
overwriteCommitted=false". In DUH2, this case is rejected and contains the
comment:
// this would need a reader to implement (to be able to check
committed
// before adding.)
Anyway, I think we'll live with it.
Thanks,
Lance Norskog
-----Original Message-----
From: Mike Klaas [mailto:[EMAIL PROTECTED]
Sent: Friday, September 07, 2007 2:47 PM
To: solr-user@lucene.apache.org
Subject: Re: adding without overriding dups - DirectUpdateHandler2.java does
not implement?
On 7-Sep-07, at 1:35 PM, Lance Norskog wrote:
> Hi-
>
> It appears that DirectUpdateHandler2.java does not actually implement
> the parameters that control whether to override existing documents.
> Should I use
No? allowDups=true ovewritePending=false overwriteCommited=false should
result in adding docs with no overwriting with DUH2.
As yonik said, overwriting is the default behaviour. It is based on
uniqueKey, which must be defined for overwriting to work.
> DirectUpdateHandler instead? Apparently DUH is slower than DUH2, but
> DUH implements these parameters. (We do so many overwrites that
> switching to DUH is probably a win.)
DUH also does not implement many newer update features, like autoCommit.
-Mike
