[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788163#action_12788163
]
Grant Ingersoll commented on SOLR-1131:
---------------------------------------
{quote}
Also, you have subFieldType="double" in the schema... and that requires that
the "double" field type be defined. Why not have subFieldSuffix="_d" and
require the "_d" dynamic field be defined? Seems like the same complexity level
{quote}
I think it makes more sense for the subFieldType to be present to be tied to a
type than a Field (subFieldSuffix), as it seems weird to have a field type have
a dependency on a Field, whereas it seems fine for a field type to have a
dependency on another field type.
{quote}
For a specific point implementation, that's fine. But if you use a point type
that can do cartesian grid stuff, then you already have different field types.
But I guess subFieldType="double" need only apply to some of the subfields (the
ones that index the points).
{quote}
I'm not sure I see this. If and when we implement CartesianPointType, it will
still need to have a type for the sub fields (depending on the tiers specified)
but I don't see why the subFieldType wouldn't be the same for all of them.
AIUI, they all have the same precision requirements.
I think part of what's missing is that for some of these attributes, it would
be better for them to be field properties and not fieldType properties. For
instance for the Cartesian case, you will need to declare what levels to
support. If that is specified on the FieldType, then you have a proliferation
of Field Type declarations, whereas if it is on the Field, that is a lot
cleaner and less verbose. I'm just not sure how that gets implemented just
yet, as having to specify startTier and endTier doesn't seem like the same
level as multiValued or stored.
> 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.
