[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788298#action_12788298
]
Grant Ingersoll commented on SOLR-1131:
---------------------------------------
bq. OK... so the real issue is that this introduces a new mechanism to look up
field types... not necessarily a horrible thing, but we should definitely think
twice before doing so.
Agreed. I'm not wedded to this approach, just want to see the discussion
through. I do feel strongly that the goal is such that an app designer should
be able to use a FieldType just as they always have, either dynamic or static.
How we get to that I don't care so much as long as it works and performs.
bq. But... that scheme seems to limit us to a single subField type (in addition
to the other downsides of requiring a new lookup mechanism).
I don't follow this. In this particular implementation, I have a single
subFieldType, but I don't see why a different implementation couldn't do
something like:
{code}
<fieldType name="foo" type="solr.MultiSubPointType" dimension="3"
subFieldTypes="double,tdouble,int"/>
{code}
bq. Aside: it looks like the code for getFieldOrNull isn't right? Seems like it
will return a field with both the wrong type and the wrong name?
Hmmm, I _think_ it should return the "owning" Schema Field, i.e. the one that
exists in the schema.xml file.
> 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.
