Details
-
Bug
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
6.1
-
None
-
None
Description
We are using configuration like this:
<!-- Creates a composite ID --> <updateRequestProcessorChain name="composite-id"> <processor class="solr.CloneFieldUpdateProcessorFactory"> <str name="source">_id</str> <str name="source">_validFrom</str> <str name="dest">_solrId</str> </processor> <processor class="solr.ConcatFieldUpdateProcessorFactory"> <str name="fieldName">_solrId</str> <str name="delimiter">-</str> </processor> <processor class="solr.LogUpdateProcessorFactory" /> <processor class="solr.RunUpdateProcessorFactory" /> </updateRequestProcessorChain>
Expected _solrId field value for document
{ "name": "Name", "_validFrom": 342230400000, "_validTo": null, "_id": "a518fad5-5421-4253-b501-0ebea0d32cd2" }
is a518fad5-5421-4253-b501-0ebea0d32cd2-342230400000
When HTTP REST is used, everything work fine.
When programmatics interface using SolrInputDocument in SolrClient is used value of _solrId will 342230400000-a518fad5-5421-4253-b501-0ebea0d32cd2 because fields are composed in order from SolrInputDocument