You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2013/10/03 01:46:43 UTC

[jira] [Commented] (SOLR-5298) user versioning

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

Yonik Seeley commented on SOLR-5298:
------------------------------------

As far as behavior, the idea would be that it works the same way as when updates are forwarded to replicas... if an older version for a document is received after a newer version, then it is silently dropped to preserve the semantics of "last one wins".

>From an API perspective, If an update specifies \_version\_, it's taken to be a constraint (optimistic concurrency).  We need either a boolean flag specifying that the supplied version is actually the one to use (userVersion=true ?) or use a different parameter alltogether (\_userVersion\_ ?)

> user versioning
> ---------------
>
>                 Key: SOLR-5298
>                 URL: https://issues.apache.org/jira/browse/SOLR-5298
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Yonik Seeley
>            Assignee: Yonik Seeley
>
> Solr currently handles the assignment of version numbers, but it would be useful to allow the user to specify their own version numbers.  For consistency, it would then be the users responsibility to specify versions on all updates (i.e. it would be undefined behavior if sometimes the user specified their own versions and sometimes did not).



--
This message was sent by Atlassian JIRA
(v6.1#6144)

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