-
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
>> -Original Message-
>> From: nos...@kaigrabfelder.de [mailto:nos...@kaigrabfelder.de]
>> Sent: Monday, February 24, 2014 7:14 PM
>> To:
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: nos...@kaigrabfelder.de [mailto:nos...@kaigrabfelder.de]
> Sent: Monday, February 24, 2014 7:14 PM
> To: java-user@lucene.apache.org
> Su
I suspect you're finding the old doc that is simply marked
as deleted. Did you check for that?
One quick way to see if this is even in the right ballpark would be
to do a forceMerge. If the problem disappears, then this is
relevant I'd guess.
Warning: The operative word here is "guess", I haven't
Hm it looks like this is somehow caused by the filters we are using for
searching.
I took one of the MY_UNIQUE_BUSINESS_ID ids, used in our applications
search functionality and debuged the lucene search a little more. If I
specify null for the filters I only get one result (which is correct).
I'll see if I can dig a little bit deeper into the 3.6 behavior, for
now I'm trying to get it running on 4.6 (as the index file is also a lot
smaller - on 3.6 it was about 2 GB for about 9000 documents, with 4.6
it's only about 200 MB).
And yes the business ID is indexed - otherwhise I would
The 30 second turnaround time in 3.6.x is absurd; if you turn on
IndexWriter's infoStream maybe it'd give a clue. Or, capture a few
stack traces and post them.
How are you creating the luceneDocumentToIndex? You must ensure that
the business ID is in fact indexed as a field in the document,
othe
Hi there,
we recently updated our application from lucene 3.0 to 3.6 with the
effect that (albeit using the SearchManager functionality as described
on
http://blog.mikemccandless.com/2011/09/lucenes-searchermanager-simplifies.html)
calls to searcherManager.maybeRefresh() were incredibly slow.
Hello,
In Lucene 4.x is there a way to get the number of documents that were deleted
from calling IndexWriter. deleteDocuments(Query)?
Another question, if we call IndexWriter. tryDeleteDocument(Reader, docId)
utilizing a near-real-time reader, what is the appropriate order to close the
reader
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
Hi all.
I'm trying to implement a form of document deletion where the previous
versions are kept around forever ( a primitive form of versioning) but
excluded from the search results.
I notice that after calling IndexWriter.deleteDocuments, even if you
close and reopen the index, the documents ar
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
I currently have code that looks like:
Term[] terms = new Term[]{
new Term( key1, value1 ),
new Term( key2, value2 )
};
writer.deleteDocuments( terms );
I want to change things such that it will delete all documents having
key2's value start with value2, i.e., if va
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
Hi,
I am trying to delete documents from an index. When using the
IndexReader#deleteDocuments(Term) method this works fine. But when using
the IndexWriter#deleteDocuments(Term) it is not working, although I am
using the same term. When using the IndexWriter I tried to commit and
optimize but
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
I'd like to delete some documents from my index. Should I use the
DeleteDocument method in the IndexReader class or the IndexModifier class? Does
it make a difference which one I use? Thank you.
_
Get more from your digital life.
riter 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 c
t; >
> > 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.
> >
> --
> V
, and I think i will cause a lock issue deleting from
> indexsearcher.
>
> best,
> -C.B.
>
--
View this message in context:
http://www.nabble.com/deleting-documents-with-doc-id-tp18619372p18679168.html
Sent from the Lucene - Java Users mailing list archive at Nabble.com.
---
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
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.
best regards,
-c.b.
: Where shall i post this issue.
you are currently posting to a list named "java-user" this is for "user"
related questions about the "java" lucene project.
if you have questions about "Lucene.Net" you should be asking them on the
"Lucene.Net" user list...
http://incubator.apache.org/lucene.net
27 jul 2007 kl. 13.43 skrev miztaken:
Can you use IndexWriter#deleteDocument instead?
No i cant use this method.
I dont know docid and i dont wanna search for it. It will only add
extra
time.
I am deleting the document on the basis of unique key field.
You can do that with IndexWriter#
re: http://www.nabble.com/file/p11827583/Program2.cs
Program2.cs
Please help me.
--
View this message in context:
http://www.nabble.com/Strange-Error-while-deleting-Documents-from-index-while-indexing.-tf4149570.html#a11827583
Sent from the Lucene - Java Users mailing list archive at N
27 jul 2007 kl. 10.50 skrev miztaken:
My application simply shut downs.
After that when i try to open the same index using IndexReader and
fetch the
document then it says "trying to access deleted document". After
getting
such error, i opened the indexWriter, optimized and then closed it.
way to do this..
Or is it that, using one instance of IndexWriter is only applicable while
doing indexing without deleting documents..?
Please make me clear.
And another question..?
What can be the possible scenario for threaded indexWriting and deleting
context..?
--
View this message in
cations\ORS Lucene Developments\July 25\
> TotalIndexingAndSearching_25_july\T otalIndexingAndSearching\
> QueryDatabaseForIndexing \Program2.cs:line 159
>
> I dont know whats the cause of this error.
>
> I am in real need of help.
> Please help me find error.
>
>
>
>
in real need of help.
Please help me find error.
--
View this message in context:
http://www.nabble.com/Strange-Error-while-deleting-Documents-from-index-while-indexing.-tf4149570.html#a11804824
Sent from the Lucene - Java Users mailing list a
diqui" <[EMAIL PROTECTED]>
10/15/2006 01:58 AM
Please respond to
java-user@lucene.apache.org
To
java-user@lucene.apache.org
cc
Subject
problem deleting documents
hi guys
i am having problem deleting documents .. apparently its not doin it..
here
is the code snippet
public v
thanks, it worked
On 10/15/06, Doron Cohen <[EMAIL PROTECTED]> wrote:
> now pk is primary key which i am storing but not indexing it..
> doc.add(new Field("pk", message.getId().toString(),Field.Store.YES,
> Field.Index.NO));
You would need to index it for this to work.
> now pk is primary key which i am storing but not indexing it..
> doc.add(new Field("pk", message.getId().toString(),Field.Store.YES,
> Field.Index.NO));
You would need to index it for this to work.
>From javadocs for IndexReader.deleteDocuments(Term):
Deletes all docum
hi guys
i am having problem deleting documents .. apparently its not doin it.. here
is the code snippet
public void delete(final BoardMessage message)
{
try{
IndexReader fsReader;
if (index.exists()) {
fsReader =IndexReader.open(index
he ID
HTH
Aviran
http://www.aviransplace.com
-Original Message-
From: Bogdan Munteanu [mailto:[EMAIL PROTECTED]
Sent: Friday, September 16, 2005 10:40 AM
To: java-user@lucene.apache.org
Subject: Deleting documents
I have a problem when deleting documents.
Lets say I have a Document objec
;m sure someone will correct me if I'm wrong!)
Cheers,
Tim.
-Original Message-
From: Bogdan Munteanu [mailto:[EMAIL PROTECTED]
Sent: 16 September 2005 15:40
To: java-user@lucene.apache.org
Subject: Deleting documents
I have a problem when deleting documents.
Lets say I have a
I have a problem when deleting documents.
Lets say I have a Document object doc.
doc.add(Field.Text("id","index1,DML"));
doc.add(Field.Text("contents","some records"));
IndexWriter.addDocument(doc);
Now if I want to delete the document with
43 matches
Mail list logo
