[jira] Updated: (SOLR-280) slightly more efficient SolrDocument implementation

["Ryan McKinley (JIRA)" <ji...@apache.org>]

     [ 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

This is a new implementation where SolrInputDocument *does not* extend SolrDocument.  This way each can be optimized for how they are most frequently used.  

This adds:

public class SolrInputField 
{
  final String name;
  float boost = 1.0f;
  Object value = null;
}

and SolrInputDocument keeps a Map<String,SolrInputField>

This still handles the distinctness bit in SolrInputDocument -- there may be a way to put the SOLR-139 logic elsewhere but i'll tackle that later.


> 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, 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.