[
https://issues.apache.org/jira/browse/SOLR-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Per Steffensen updated SOLR-3173:
---------------------------------
Description:
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)
The essence of this issue is to be able to state your intent (insert or update)
and have slightly different semantics (from each other and the existing update)
depending on you intent.
The functionality provided by this issue is only really meaningfull when you
run with "updateLog" activated.
This issue might be solved more or less at the same time as SOLR-3178, and only
one single SVN patch might be given to cover both issues.
was:
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)
> 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)
> The essence of this issue is to be able to state your intent (insert or
> update) and have slightly different semantics (from each other and the
> existing update) depending on you intent.
> The functionality provided by this issue is only really meaningfull when you
> run with "updateLog" activated.
> This issue might be solved more or less at the same time as SOLR-3178, and
> only one single SVN patch might be given to cover both issues.
--
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: [email protected]
For additional commands, e-mail: [email protected]
