We haven't changed Solr versions. We've been using 3.1.0 all along. Plus, I have some code that runs during indexing and retrieves the fields from a SolrInputDocument, rather than a SolrDocument. That code gets Strings without any problem, and always has, even without saying multiValued="false".
-Rich -----Original Message----- From: Chris Hostetter [mailto:hossman_luc...@fucit.org] Sent: Thursday, June 16, 2011 2:18 PM To: solr-user@lucene.apache.org Cc: Simon, Richard T Subject: RE: getFieldValue always returns an ArrayList? : and all of a sudden I get Strings. But, doesn't multivalued default to : false? In my schema, I originally did not set multivalued. I only put in : multivalued="false" after I experienced this issue. That's dependent on the version of Solr, and it's is where the "version" property of the schema comes in. (as the default behavior in solr changes, it does so dependent on what "version" you specify in your schema to prevent radical behavior changes if you upgrade but keep the same configs)... <schema name="example" version="1.4"> <!-- attribute "name" is the name of this schema and is only used for display purposes. Applications should change this to reflect the nature of the search collection. version="1.4" is Solr's version number for the schema syntax and semantics. It should not normally be changed by applications. 1.0: multiValued attribute did not exist, all fields are multiValued by nature 1.1: multiValued attribute introduced, false by default 1.2: omitTermFreqAndPositions attribute introduced, true by default except for text fields. 1.3: removed optional field compress feature 1.4: default auto-phrase (QueryParser feature) to off --> -Hoss