Changes between Version 2 and Version 3 of FastIndexUpdate


Ignore:
Timestamp:
02/21/13 01:11:22 (12 years ago)
Author:
jesseeichar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FastIndexUpdate

    v2 v3  
    5757A potential solution comes to mind:
    5858
    59  * Create 2 documents from metadata xml
    60   * a document only containing fields with stored data
    61   * a document containing fields only with non-stored data
    62  * Insert both documents into index
    63 
    64 Now the document with stored fields can be updated without losing any data. 
    65 
    66 Obviously this impacts how searching is done.  First it means that searches that involve both stored and non-stored fields need to be split and recombined.
    67 
    68 For example &(any:water title:salt)
    69 
    70 if title is stored and any is not then two searches have to be combined and documents that are in both searches (based on metadata id) are the true results.  Ordering of results will be very difficult.
    71 
     59Lucene 4 has the concept of flexible indexing (http://java.dzone.com/videos/heavy-committing-flexible) 
    7260
    7361=== Backwards Compatibility Issues ===