[
https://issues.apache.org/jira/browse/SOLR-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yonik Seeley updated SOLR-3743:
-------------------------------
Attachment: SOLR-3743.patch
I tried to create a test case, but for some reason it doesn't seem to have the
same behavior as the example above...
> stored copyField targets, optimistic concurrency, atomic updates
> ----------------------------------------------------------------
>
> Key: SOLR-3743
> URL: https://issues.apache.org/jira/browse/SOLR-3743
> Project: Solr
> Issue Type: Bug
> Reporter: Yonik Seeley
> Priority: Blocker
> Fix For: 4.0
>
> Attachments: SOLR-3743.patch
>
>
> Stored copyField targets do not work well with other solr features.
> Consider the following getting started guide:
> http://yonik.com/solr/getting-started/
> After the document update, a get of the resulting document reveals:
> {code}/opt/code/lusolr/solr$ curl http://localhost:8983/solr/get?id=book1
> {
> "doc":
> {
> "id":"book1",
> "title":["American Gods"],
> "author":"Neil Gaiman",
> "author_s":["Neil Gaiman",
> "Neil Gaiman"],
> "cat":["fantasy"],
> "pubyear_i":2001,
> "ISBN_s":"0-380-97365-0",
> "_version_":1410692581016207360}}
> {code}
> note the double author_s.
> A user using realtime-get and optimistic concurrency may run across the same
> issue. The other field stored field that is a copyField target is price_c.
--
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]
