[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780955#action_12780955
]
Chris Male commented on SOLR-1131:
----------------------------------
My initial feeling is, is searching against just one field something this
functionality needs to concern itself with? If someone creates a field of type
Point for example, which behind the scenes is indexed as 2 fields, from a Solr
schema.xml perspective it is just 1 field, and so it should be the same at the
querying level. We are trying to encapsulate the fact that the FieldType
results in multiple fields. This then frees us up to choose a naming
convention that is easy for us to implement, because we don't have to concern
users with the convention.
If someone does want to be able to search against just one field, such as maybe
being able to find documents at a certain x coordinate, rather than an x,y
Point, then I think we can simply recommend they index that data in a separate
field.
> 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.
