[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780954#action_12780954
]
Grant Ingersoll edited comment on SOLR-1131 at 11/21/09 12:11 PM:
------------------------------------------------------------------
I'm also looking for ideas on how to handle the naming of the fields that are
produced by this. I think a FieldType that produces multiple fields should
hide the logistics of the naming, which this patch doesn't even begin to
scratch the surface of and also on the search side, how does one search against
just one of the fields?
Would appreciate thoughts on that.
was (Author: gsingers):
I'm also looking for ideas on how to handle the naming of the fields that
are produced by this. I think a FieldType that produces multiple fields should
hide the logistics of the naming, which this patch doesn't even begin to
scratch the surface of and also on the search side, how does one search against
just one of the fields?
Would appreciated thoughts on that.
> 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.
