[
https://issues.apache.org/jira/browse/SOLR-12887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656929#comment-16656929
]
Christine Poerschke commented on SOLR-12887:
--------------------------------------------
Attached draft illustrative patch. Intuitively:
* an add/update to redate the document within its existing collection should be
just fine, but
* an add/update that changes the timestamp to a value outside the existing
collection would result in two documents in two collections.
* If two documents are not what is intended by the client then they can do a
delete followed by an add instead of just an add/update alone.
Interestingly the draft patch in its current form suggests that query behaviour
is variable when two TRA collections have a document with the same key i.e.
sometimes it says "found 1" and sometimes it says "found 2" even if
"cache=false" was sent in the query. Could be to do with which url the test's
CloudSolrClient used for the requests, haven't yet looked into further.
> TRA: document re-dating (question, test, docs)
> ----------------------------------------------
>
> Key: SOLR-12887
> URL: https://issues.apache.org/jira/browse/SOLR-12887
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Christine Poerschke
> Priority: Minor
> Attachments: SOLR-12887.patch
>
>
> This ticket is sort of a combination of a question with small test and
> documentation additions.
> After a document is added, can subsequent updates to it include a change of
> its timestamp? What happens if a timestamp change logically 'moves' the
> document out of its original collection?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
