[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780961#action_12780961
]
Chris Male commented on SOLR-1131:
----------------------------------
Those are definitely big problems.
The ResponseWriter problem could be simplified if they used SolrDocuments
rather than retrieving raw Lucene Documents. When constructing the
SolrDocuments, which is done in cooperation with an IndexSchema instance, we
have the information needed to bring the multiple fields together as one. I'm
not sure of the performance impact of doing this, but it seems like having the
ResponseWriters retrieve the data in a single consistent fashion is a good
thing in the long run anyway.
> Allow a single field type to index multiple fields
> --------------------------------------------------
>
> Key: SOLR-1131
> URL: https://issues.apache.org/jira/browse/SOLR-1131
> Project: Solr
> Issue Type: New Feature
> Components: Analysis
> Reporter: Ryan McKinley
> Assignee: Grant Ingersoll
> Attachments: SOLR-1131-IndexMultipleFields.patch, SOLR-1131.patch
>
>
> In a few special cases, it makes sense for a single "field" (the concept) to
> be indexed as a set of Fields (lucene Field). Consider SOLR-773. The
> concept "point" may be best indexed in a variety of ways:
> * geohash (sincle lucene field)
> * lat field, lon field (two double fields)
> * cartesian tiers (a series of fields with tokens to say if it exists within
> that region)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
