FAQ
Hi all,

The JavaDocs do not appear to mention that only stored fields persist
IndexWriter.updateDocument. When opening new readers, from either
IndexWriter.getReader or IndexReader.open, neither TermDocs nor IndexSearcher
will find terms in fields which weren't stored.

Existing readers, however, do continue to find such terms after updateDocument
has been called. At best, this is confusing. Is this a defect?

Thanks,
Justin




---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org

Search Discussions

  • Steven A Rowe at Oct 4, 2010 at 6:07 pm
    This is not a defect: <http://wiki.apache.org/lucene-java/LuceneFAQ#Does_Lucene_allow_searching_and_indexing_simultaneously.3F>.
    -----Original Message-----
    From: Justin
    Sent: Monday, October 04, 2010 2:03 PM
    To: java-user@lucene.apache.org
    Subject: Updating documents with fields that aren't stored

    Hi all,

    The JavaDocs do not appear to mention that only stored fields persist
    IndexWriter.updateDocument. When opening new readers, from either
    IndexWriter.getReader or IndexReader.open, neither TermDocs nor
    IndexSearcher
    will find terms in fields which weren't stored.

    Existing readers, however, do continue to find such terms after
    updateDocument
    has been called. At best, this is confusing. Is this a defect?

    Thanks,
    Justin




    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-user-help@lucene.apache.org
  • Justin at Oct 4, 2010 at 6:15 pm
    Even for IndexWriter.getReader (near real-time)? "changes made during an
    IndexWriter session can be quickly made available for searching without closing
    the writer nor calling commit(long)."

    http://lucene.apache.org/java/3_0_2/api/all/org/apache/lucene/index/IndexWriter.html#getReader()





    ----- Original Message ----
    From: Steven A Rowe <sarowe@syr.edu>
    To: "java-user@lucene.apache.org" <java-user@lucene.apache.org>
    Sent: Mon, October 4, 2010 1:05:36 PM
    Subject: RE: Updating documents with fields that aren't stored

    This is not a defect:
    <http://wiki.apache.org/lucene-java/LuceneFAQ#Does_Lucene_allow_searching_and_indexing_simultaneously.3F>.

    -----Original Message-----
    From: Justin
    Sent: Monday, October 04, 2010 2:03 PM
    To: java-user@lucene.apache.org
    Subject: Updating documents with fields that aren't stored

    Hi all,

    The JavaDocs do not appear to mention that only stored fields persist
    IndexWriter.updateDocument. When opening new readers, from either
    IndexWriter.getReader or IndexReader.open, neither TermDocs nor
    IndexSearcher
    will find terms in fields which weren't stored.

    Existing readers, however, do continue to find such terms after
    updateDocument
    has been called. At best, this is confusing. Is this a defect?

    Thanks,
    Justin




    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-user-help@lucene.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-user-help@lucene.apache.org
  • Steven A Rowe at Oct 4, 2010 at 6:20 pm
    Yes, even for IW.getReader() - from <http://wiki.apache.org/lucene-java/NearRealtimeSearch>:

    Now Lucene offers a unified API where one calls getReader
    and any updates are immediately searchable.

    I.e., the reader returned by getReader doesn't track updates; it too represents a shapshot in time. It's just less costly to reopen.

    -----Original Message-----
    From: Justin
    Sent: Monday, October 04, 2010 2:15 PM
    To: java-user@lucene.apache.org
    Subject: Re: Updating documents with fields that aren't stored

    Even for IndexWriter.getReader (near real-time)? "changes made during an
    IndexWriter session can be quickly made available for searching without
    closing
    the writer nor calling commit(long)."

    http://lucene.apache.org/java/3_0_2/api/all/org/apache/lucene/index/IndexW
    riter.html#getReader()





    ----- Original Message ----
    From: Steven A Rowe <sarowe@syr.edu>
    To: "java-user@lucene.apache.org" <java-user@lucene.apache.org>
    Sent: Mon, October 4, 2010 1:05:36 PM
    Subject: RE: Updating documents with fields that aren't stored

    This is not a defect:
    <http://wiki.apache.org/lucene-
    java/LuceneFAQ#Does_Lucene_allow_searching_and_indexing_simultaneously.3F>
    .

    -----Original Message-----
    From: Justin
    Sent: Monday, October 04, 2010 2:03 PM
    To: java-user@lucene.apache.org
    Subject: Updating documents with fields that aren't stored

    Hi all,

    The JavaDocs do not appear to mention that only stored fields persist
    IndexWriter.updateDocument. When opening new readers, from either
    IndexWriter.getReader or IndexReader.open, neither TermDocs nor
    IndexSearcher
    will find terms in fields which weren't stored.

    Existing readers, however, do continue to find such terms after
    updateDocument
    has been called. At best, this is confusing. Is this a defect?

    Thanks,
    Justin




    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-user-help@lucene.apache.org



    ---------------------------------------------------------------------
    To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
    For additional commands, e-mail: java-user-help@lucene.apache.org

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupjava-user @
categorieslucene
postedOct 4, '10 at 6:03p
activeOct 4, '10 at 6:20p
posts4
users2
websitelucene.apache.org

2 users in discussion

Steven A Rowe: 2 posts Justin: 2 posts

People

Translate

site design / logo © 2022 Grokbase