[SOLR-2193] Re-architect Update Handler

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 4.0-ALPHA
• Assignee: Mark Miller
• Reporter: Mark Miller
• Created: 25/Oct/10 02:06
• Updated: 10/May/13 10:39
• Resolved: 30/Jun/11 14:05

Description

The update handler needs an overhaul.

A few goals I think we might want to look at:

1. Cleanup - drop DirectUpdateHandler(2) line - move to something like UpdateHandler, DefaultUpdateHandler
2. Expose the SolrIndexWriter in the api or add the proper abstractions to get done what we now do with special casing:
if (directupdatehandler2)
success
else
failish
3. Stop closing the IndexWriter and start using commit (still lazy IW init though).
4. Drop iwAccess, iwCommit locks and sync mostly at the Lucene level.
5. Keep NRT support in mind.
6. Keep microsharding in mind (maintain logical index as multiple physical indexes)
7. Address the current issues we face because multiple original/'reloaded' cores can have a different IndexWriter on the same index.

Issue Links

• incorporates: SOLR-3587 After reloading a SolrCore, the original Analyzer is still used rather than a new one.
• is related to: SOLR-1155 Change DirectUpdateHandler2 to allow concurrent adds during an autocommit
• is related to: SOLR-2437 Use IndexWriter.deleteAll() in DUH2.deleteAll() instead of closing and reopening writer w/ create=true
• is superceded by: SOLR-2565 Prevent IW#close and cut over to IW#commit