[
https://issues.apache.org/jira/browse/SOLR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Johnson updated SOLR-280:
------------------------------
Attachment: SOLR-280-SolrDocument2-API-Compatibility.patch
>The API changes mostly affect solrj users.
being one of those heavily affected users i created the attached patch to make
us unaffected. (or at least i went from a few hundred compile errors to 0)
the following methods were added back and are mostly 1-5 line wrappers to the
existing methods or underlying datastructures.
setField(String, Object)
getFieldValue(String)
getFieldValues(String)
addField(String, Object)
getFieldNames()
- will
> slightly more efficient SolrDocument implementation
> ---------------------------------------------------
>
> Key: SOLR-280
> URL: https://issues.apache.org/jira/browse/SOLR-280
> Project: Solr
> Issue Type: Improvement
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Priority: Minor
> Attachments: SOLR-280-SolrDocument2-API-Compatibility.patch,
> SOLR-280-SolrDocument2.patch, SOLR-280-SolrDocument2.patch
>
>
> Following discussion in SOLR-272
> This implementation stores fields as a Map<String,Object> rather then a
> Map<String,Collection<Object>>. The API changes slightly in that:
> getFieldValue( name ) returns a Collection if there are more then one fields
> and a Object if there is only one.
> getFirstValue( name ) returns a single value for the field. This is intended
> to make things easier for client applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
