lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-2664) Disable/enable autocommit on the fly
Date Tue, 13 Dec 2011 23:41:29 GMT

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

Hoss Man commented on SOLR-2664:
--------------------------------

I'm not sure i really understand the "batch" suggestion, but if the general idea of the overall
issue is that in some solr instances, some clients know they don't need autocommit, the clean
solution (in my mind) would be for these solr instances to be configured such that...

* there *is not* a global autocommit for the update handler
* there *is* a default commitWithin value configured for all of the Update RequestHandlers
(ie "/update", "/update/javabin", etc...)

...making requests default to "auto commit" within a configured time frame, but clients that
don't want that can override by specifying {{commitWithin=-1}} in the request.

that would satisfy all of the requested functionality w/o new code complexity right?  (and
most importantly to my mind: wouldn't introduce new stateful behavior in Solr preventing autocommit
that clients could trigger w/o Solr admins realizing/understanding/allowing)
                
> Disable/enable autocommit on the fly
> ------------------------------------
>
>                 Key: SOLR-2664
>                 URL: https://issues.apache.org/jira/browse/SOLR-2664
>             Project: Solr
>          Issue Type: New Feature
>          Components: update
>    Affects Versions: 4.0
>            Reporter: Simon Rosenthal
>            Priority: Minor
>             Fix For: 4.0
>
>         Attachments: SOLR-2664.patch
>
>
> There are occasions when although autocommit is configured, it would be desirable to
disable it temporarily - for instance when batch adding/updating a set of documents which
should be committed atomically (e.g. a set of price changes).
> The patch adds <disableAutoCommit/> and </enableAutoCommit> commands to XMLUpdateHandler,
and also adds a disableAutoCommit=true|false attribute to the <add> element - this will
disable autocommit until the terminating </add> at the end of the XML document is reached.
> At present, the autocommit state will not survive a core reload.
> It should be possible to extend this functionality to SolrJ, CSVUpdatehandler ( and JSONUpdateHandler
?)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message