You're making a common mistake as to the meaning of multiValued. The
input doc should look something like (xml format)

<add>
  <doc>
     <field name="mv_int_field">1</field>
    <field name="mv_int_field">2</field>
  </doc>
</add>

Each "mv_int_field" is a separate, complete single integer. But there
can be a many of them.

when you specify
   <field name="mv_int_field">1,2,3</field>

you're telling Solr that the _single_ value of the field is "1,2,3"
which, of course, doesn't parse as an integer.

Best,
Erick



On Wed, Sep 6, 2017 at 1:09 PM, Steve Pruitt <bpru...@opentext.com> wrote:
> Can't get a multi-valued pint field to update.
>
> The schema defines the field:  <field name="dnis" type="pints" 
> multiValued="true" required="false" docValues="true" stored="true"/>
>
> I get the exception on this input:  <field name="dnis">7780386,7313483</field>
>
> Caused by: java.lang.NumberFormatException: For input string: "7780386, 
> 7313483"
>         at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
>         at java.lang.Integer.parseInt(Integer.java:580)
>         at java.lang.Integer.parseInt(Integer.java:615)
>         at 
> org.apache.solr.schema.IntPointField.createField(IntPointField.java:181)
>         at org.apache.solr.schema.PointField.createFields(PointField.java:216)
>         at 
> org.apache.solr.update.DocumentBuilder.addField(DocumentBuilder.java:72)
>         at 
> org.apache.solr.update.DocumentBuilder.toDocument(DocumentBuilder.java:179)
>
> Not sure why the parser thinks the values are strings.  I don't see any 
> non-numeric extraneous characters.
>
> Do I need docValues and multivalued in my field definition, since they are 
> defined on the pints field type?
>
> Thanks.
>
> -Steve

Reply via email to