[
https://issues.apache.org/jira/browse/SOLR-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller reassigned SOLR-2193:
---------------------------------
Assignee: Mark Miller
I've updated my patch to trunk.
You can find the most recent work here:
https://github.com/markrmiller/Lucene-Solr-Lab/commit/051995d50160e7081854febd471e72b9e81b8a3f
I'll upload a patch after I start lazy creating the IndexWriter.
This can be a fairly large win on time to visibility - you don't wait for
background merges to finish before opening a new IndexReader now.
It's also a start at solving our rather nasty reload a core, briefly different
writers on the same index problem (usually avoided because the overlap is brief
and the IndexWriter created lazily).
It's still early work. Issues remain.
> Re-architect Update Handler
> ---------------------------
>
> Key: SOLR-2193
> URL: https://issues.apache.org/jira/browse/SOLR-2193
> Project: Solr
> Issue Type: Improvement
> Reporter: Mark Miller
> Assignee: Mark Miller
> Fix For: Next
>
>
> 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)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
