Changes between Version 1 and Version 2 of FastIndexUpdate


Ignore:
Timestamp:
Feb 21, 2013, 12:25:51 AM (11 years ago)
Author:
jesseeichar
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FastIndexUpdate

    v1 v2  
    44|| '''Contact(s)''' || [http://wiki.osgeo.org/wiki/User:Jeichar Jesse Eichar] ||
    55|| '''Last edited''' || ||
    6 || '''Status''' || Proposal ||
     6|| '''Status''' || Not proposed. Just brain storm ||
    77|| '''Assigned to release''' || 2.9.x ||
    88|| '''Resources''' || Swisstopo ||
     
    5353 1. insert modified document to index
    5454
     55However this is a naive solution and fails in practice because there are both stored and non-stored fields.  Using this strategy will lose the non-stored fields. 
     56
     57A potential solution comes to mind:
     58
     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
     64Now the document with stored fields can be updated without losing any data. 
     65
     66Obviously 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
     68For example &(any:water title:salt)
     69
     70if 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.
    5571
    5672