[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788123#action_12788123
]
Grant Ingersoll commented on SOLR-1131:
---------------------------------------
{quote}
Regarding polyfields... it's not clear why they are special enough to have to
change the IndexSchema? (IndexSchema.isPolyField, getPolyField,
getPolyFieldType, getPolyFieldTypeNoEx, etc). Can't we just store them as
normal field types?
{quote}
My thinking was that a Query Parser or other things might need to know look up
this information, but you are right, I don't have a specific use case for them
at the moment. At the same time, poly fields _feel_ like a hybrid between
regular fields and dynamic fields and thus fit at the same level they do.
> 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: Schema and Analysis
> Reporter: Ryan McKinley
> Assignee: Grant Ingersoll
> Fix For: 1.5
>
> Attachments: SOLR-1131-IndexMultipleFields.patch, SOLR-1131.patch,
> SOLR-1131.patch, SOLR-1131.patch, SOLR-1131.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.
