On Tue, Mar 16, 2010 at 20:45, Rene Hackl-Sommer wrote:
> Hi Daniel,
>
> Unless you have only a few documents and a small index, I don't think never
> calling optimize is going to be a means you should rely upon.
>
> What about if you reindexed the documents you are deleting, adding a field
> wit
I cannot comment on the "marked-as-deleted" documents, but for the
approach I outlined: this might impact the scores. I prefer to say
'impact' instead of 'skew', because to me 'skew' would imply that the
original scores are some kind of ideal state which is distorted. I don't
think this is nece
Wouldn't these excluded/filtered documents skew the scores even though they
are supposed to be marked as deleted? Don't the idf values used in scoring
depend on the entire document set and not just the matching hits for a
query?
Thanks,
TCK
On Tue, Mar 16, 2010 at 5:45 AM, Rene Hackl-Sommer wr
Hi Daniel,
Unless you have only a few documents and a small index, I don't think
never calling optimize is going to be a means you should rely upon.
What about if you reindexed the documents you are deleting, adding a
field with the value "true"? This would imply that
either
1) all fields
An incidental merge will delete them.
I think you'll have to maintain your own filter... but it shouldn't be
that large? Ie it's as large as deleted docs BitVector would be
anyway... except that the docs never go away.
Mike
On Mon, Mar 15, 2010 at 11:20 PM, Daniel Noll wrote:
> Hi all.
>
> I'm
There are IndexWriter.deleteDocuments methods that take queries.
Passing a TermQuery and a WildcardQuery to
writer.deleteDocuments(Query[]) should do the trick.
--
Ian.
On Tue, Oct 27, 2009 at 3:10 AM, Paul J. Lucas wrote:
> I currently have code that looks like:
>
> Term[] terms = new Term
been there, done that .
On Fri, Dec 5, 2008 at 9:17 AM, Gunnar Wurl <[EMAIL PROTECTED]> wrote:
> Thanks for your answer Erick..
>
> I just found out that my problem occured because of an user(me) error. Used
> two different workspaces and indexes.. sorry.
>
> Erick Erickson schrieb:
>
> How do y
Thanks for your answer Erick..
I just found out that my problem occured because of an user(me) error.
Used two different workspaces and indexes.. sorry.
Erick Erickson schrieb:
How do you know it's failing? If you're searching could it be
that you need to re-open the underlying indexreader wh
How do you know it's failing? If you're searching could it be
that you need to re-open the underlying indexreader when
you delete using IndexWriter?
Best
Erick
On Fri, Dec 5, 2008 at 8:42 AM, Gunnar Wurl <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I am trying to delete documents from an index. When usi
OK, thank you.
> From: [EMAIL PROTECTED]
> To: java-user@lucene.apache.org
> Subject: Re: Deleting documents ...
> Date: Sun, 10 Aug 2008 10:52:42 -0400
>
>
> Actually it's usually best to use the deleteDocuments method in
> IndexWriter since it saves you hav
Actually it's usually best to use the deleteDocuments method in
IndexWriter since it saves you having to close/open IndexWriter &
IndexReader back and forth to do the deletions.
IndexModifier is deprecated.
Mike
Dragon Fly wrote:
I'd like to delete some documents from my index. Should I
well just checked the api, the deleteDocuments(term[]) method deletes any
document containing any of the terms.
I think I will go to the trunk version.
best.
-c.a.
On Sat, Aug 2, 2008 at 12:14 AM, Cam Bazz <[EMAIL PROTECTED]> wrote:
>
> from what I understand:
> there is a deleteDocuments by a
from what I understand:
there is a deleteDocuments by a term array method?
I was asking if there was a side effect of deleting from indexReader that i
get from an indexsearcher and not the writer.
Best.
On Sun, Jul 27, 2008 at 9:44 PM, Karsten F.
<[EMAIL PROTECTED]>wrote:
>
> Hi,
>
> only to b
Hi,
only to be sure:
You know IndexModifier.deleteDocument(int)?
It is deprecated, because you should use
IndexWriter.deleteDocuments(Term[]).
What do you mean with "index is committed".
If you mean "optimize()" the document number will change (so there is a
side-effect;-)
best regards
Karste
hello,
the thing is:
I got a indexwriter and indexsearcher.
I do a indexsearcher.getIndexReader.delete(int id)
would not that cause problems? there is not a way to delete from
indexwriter, and I think i will cause a lock issue deleting from
indexsearcher.
best,
-C.B.
On Thu, Jul 24, 2008 at 2
23 jul 2008 kl. 22.08 skrev Cam Bazz:
hello -
if I make a query and get the document ids and delete with the
document id -
could there be a side effect?
my index is committed periodically, but i can not say when it is
committed.
The only thing is that the deltions will not be visible u
Because when you add a document, the id is going thru an Analyzer, which
in your case uses a low case filter, but when you create a Term object
the term is not lower cased by an Analyzer.
If instead of using Field.Text for your ID, you'll use Keyword, then the
Analyzer will not lower case the ID
If you're indexing a field like this in order to be able to use it as a
reference later, you should normally index it using Field.Keyword
instead of Field.Text - if you use Text, it will go through your
Analyzer, which is probably what's changing the case. (I think this is
right - I'm sure someone
18 matches
Mail list logo
