Hi, I recently discovered that the copyFields directive exclusively works for copying fields from the input doc to the indexed/stored doc. I'd like to be able to do the following:
excerpt from schema.xml: <field name="a" type="grandVoodoo" indexed="true" stored="true" multiValue="true"/> <field name="b" type="trimmedString" indexed="true" stored="true" multiValue="true"/> <copyField source="someInputField1" dest="a" /> <copyField source="someInputField2" dest="a" /> <copyField source="someInputField3" dest="a" /> <copyField source="a" dest="b" /> <copyField source="someInputField4" dest="b" /> where only "someInputField1..4" is specified in the doc in the update command. The goal is not to have to redundantly specify the whole analyzer/copyFields voodoo for the "b" field. Am I correct that this is currently only possible by specifying: <field name="a" type="grandVoodoo" indexed="true" stored="true" multiValue="true"/> <field name="b" type="trimmedString" indexed="true" stored="true" multiValue="true"/> <copyField source="someInputField1" dest="a" /> <copyField source="someInputField2" dest="a" /> <copyField source="someInputField3" dest="a" /> <copyField source="someInputField1" dest="b" /> <copyField source="someInputField2" dest="b" /> <copyField source="someInputField3" dest="b" /> <copyField source="someInputField4" dest="b" /> where I also have to decide wether to analyze all input on "b" with the trimmedString or the grandVoodoo analyzer.. thanks, Axel -- View this message in context: http://www.nabble.com/cahining-copyFields-tp19839265p19839265.html Sent from the Solr - User mailing list archive at Nabble.com.
