[
https://issues.apache.org/jira/browse/SOLR-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219104#comment-13219104
]
Per Steffensen commented on SOLR-3173:
--------------------------------------
Thanks for great input Yonik Seeley. I belive you are already commenting on the
related Jira issue that I havnt created yet :-) This issue SOLR-3173 is not so
much about versioning but basically only about being able to state your intent
(insert or update) on Solr updates, and support failing on "insert"-intent if
document already exists, and doing nothing on "update"-intent if document does
not already exist.
I want to reply a little to you comment here anyway:
I fell over the _version_ field, and wanted to ask about what it is used for.
Can you point me in the direction of a (Wiki) description explaining more
exactly what it is used for and how. Or else I will need to read the code, in
order to make sure that I agree that we can just use that version number - or
to what degree we can use it.
I am not sure I ALWAYS like optimistic locking on a per-request basis. Then it
is "too much" up to the clients to use it "correctly". So it depends on how
much control you have over your clients. I have different thoughts on this area
though. Those thoughts will be reflected soon in a change of the description of
this issue and the upcomming related issue (the one actually dealing with
versions). Please be patient.
Providing me more info about the _version_ would be greatly appreciated now,
though :-)
> Database semantics - insert and update
> --------------------------------------
>
> Key: SOLR-3173
> URL: https://issues.apache.org/jira/browse/SOLR-3173
> Project: Solr
> Issue Type: New Feature
> Components: update
> Affects Versions: 3.5
> Environment: All
> Reporter: Per Steffensen
> Assignee: Per Steffensen
> Labels: RDBMS, insert, nosql, uniqueKey, update
> Fix For: 4.0
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> In order increase the ability of Solr to be used as a NoSql database (lots of
> concurrent inserts, updates, deletes and queries in the entire lifetime of
> the index) instead of just a search index (first: everything indexed (in one
> thread), after: only queries), I would like Solr to support the following
> features inspired by RDBMSs and other NoSql databases.
> * Given a solr-core with a schema containing a uniqueKey-field "uniqueField"
> and a document Dold, when trying to INSERT a new document Dnew where
> Dold.uniqueField is equal to Dnew.uniqueField, then I want a
> DocumentAlredyExists error. If no such document Dold exists I want Dnew
> indexed into the solr-core.
> * Given a solr-core with a schema containing a uniqueKey-field "uniqueField"
> and a document Dold, when trying to UPDATE a document Dnew where
> Dold.uniqueField is equal to Dnew.uniqueField I want Dold deleted from and
> Dnew added to the index (just as it is today).If no such document Dold exists
> I want nothing to happen (Dnew is not added to the index)
--
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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
