[
https://issues.apache.org/jira/browse/SOLR-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett resolved SOLR-4673.
-------------------------------------
Resolution: Invalid
AFAICT, this bug report is against a feature that hasn't been committed
(SOLR-3178) - there's nothing in current Lucene/Solr code base for
{{semanticMode}}, the only place I found it mentioned beyond the wiki article
(which also says it's not committed) is on SOLR-3178. Since the feature hasn't
been committed, I'm not sure there's a reason to keep this issue forever. I
linked the issues, though in case that feature gets picked back up again in the
future.
> semanticsMode consistency acts like classic-consistency-hybrid
> --------------------------------------------------------------
>
> Key: SOLR-4673
> URL: https://issues.apache.org/jira/browse/SOLR-4673
> Project: Solr
> Issue Type: Bug
> Components: update
> Affects Versions: 4.1
> Reporter: Sam Kass
> Labels: concurrency, optimistic
>
> Code like the following, run with semanticsMode set to "consistency", should
> fail on the second doc. Instead, it's acting like
> classic-consistency-hybrid, where it treats the second doc as if it should
> always overwrite. (Going by docs in
> http://wiki.apache.org/solr/Per%20Steffensen/Update%20semantics as it's the
> only place where this feature added 2 releases ago is as yet documented.)
> {quote}
> String id = UUID.randomUUID().toString();
> SolrInputDocument docA = new SolrInputDocument();
> docA.addField("id", id);
> docA.addField("_version_", -1);
> SolrInputDocument docB = new SolrInputDocument();
> docB.addField("id", id);
> // intentionally omit _version_
> solrServer.add(docA);
> solrServer.add(docB);
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
