[
https://issues.apache.org/jira/browse/SOLR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-280:
-------------------------------
Attachment: SOLR-280-SolrDocument2.patch
We could go further and store boosted values as:
class BoostedValue {
float boost;
Object value;
}
but I think that makes the implementation to convoluted. If we went this
route, we would need to check each value before passing it back to the client.
> 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.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.
