On 26/07/2012, at 11:55 PM, Lewis John Mcgibbney wrote: > Can you not just add multiValued="true" to your content field then > specify the correct mapping? This will map stripedContent to Content > as well as Content to Content.
I was reluctant to do this because the schema is tightly tied to a Solr integration component for a CMS. Also there are a number of copyfield directives based on the field and altering it to multivalue could introduce odd behaviour into the wider system. I've now resolved the issue with what turned out to be a simple fix (just needed a bit of a lateral approach). In solrmappingindex.xml I mapped the content field to a non-existant field which the schema.xml is configured to ignore and then mapped the strippedContent field to content - works like a charm. If you miss that first re-assignment you get the multiValue exception error.
