never mind, the issue ended up being that i had the copyField for that uom field in two places and hadn't realized it, doh!
-- *John Blythe* Product Manager & Lead Developer 251.605.3071 | j...@curvolabs.com www.curvolabs.com 58 Adams Ave Evansville, IN 47713 On Tue, May 24, 2016 at 9:05 AM, John Blythe <j...@curvolabs.com> wrote: > hi all, > > i'm going mad over something that seems incredibly simple. in an attempt > to maintain some order to my growing data, i've begun to employ > dynamicFields. basic stuff here, just using *_s, *_d, etc. for my strings, > doubles, and other common datatypes. > > i have these stored but not indexed. i'm then using copyFields to copy > them over to other fields. for instance, vendorItem_s would copy into > vendorItem_ng (ngram), vendorItem (a simple text_split), etc. > > one of the fields keeps throwing an error on my import attempts. i'm > guessing it'll occur on other fields, too, but this one throws the first > tripwire. it's my uom field, unit of measure. it contains a single value > per row/doc, e.g. "EA" or "BX." > > i get the following error on import: "multiple values encountered for non > multiValued copy field uom: EA" > > i don't want this field to be multivalued and there is no reason it needs > to be. is this something innate to dynamicField or copyField? > > thanks for any info- >
