[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788151#action_12788151
]
Grant Ingersoll commented on SOLR-1131:
---------------------------------------
bq. What if, instead, dynamic fields are directly used for subfields?
That then requires those dynamic fields to be present, which I'd rather not
have to do. Part of the goal of this issue is to hide the implementation.
Having said that, I still don't know whether that means I need to keep the
IndexSchema changes. Let me do another iteration.
bq. Another thing to keep in mind - not all subfields will always be of the
same type.
Agreed, but I don't think this is baked in to the generic capabilities, just
the Point stuff, where I think it is fine to have the same sub-type.
> 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.
