[ 
https://issues.apache.org/jira/browse/SOLR-2193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041307#comment-13041307
 ] 

Mark Miller commented on SOLR-2193:
-----------------------------------

P.S. While it may not be believed, there are no politics behind this issue :) I 
did not intentionally side step any other issues - nor did Lucid even initiate 
that I work on this.

I wanted to fix the update handler - I didn't want to let any history or pre 
conceived notions get in my way. Was I successful at that? I don't know. But I 
approached this as blank slate as I could - if I could change the update 
handler, what would I do? I didn't look at what anyone else had done. So far, 
this is it.

The community can take my effort or reject it, just like any others out there. 
The motivation of this issue, as far as I am concerned, is my own self interest 
in doing some interesting coding, and my good will towards Lucene/Solr. Any 
other motivations where so minor they don't even register.

Take it or leave - I'm not looking to cram this down anyones throat.

> 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: 4.0
>
>         Attachments: SOLR-2193.patch, SOLR-2193.patch, SOLR-2193.patch, 
> SOLR-2193.patch
>
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to