[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788103#action_12788103
]
Yonik Seeley commented on SOLR-1131:
------------------------------------
bq. 1. Why is TextField overriding getFieldQuery when it isn't called, except
possibly via the FieldQParserPlugin?
As you point out, it is called by FieldQParserPlugin, and it's a move to make
things a bit more orthogonal - with a little more work it could even be used by
the SolrQueryParser for text field types as well. It also opened the (expert)
possibility of creating a new TextField type that handled things a bit
differently.
bq. 2. I'm not sure I understand the getDistance, getBoundingBox methods on the
GeoFieldType. It seems like that precludes one from picking a specific distance
(for instance, some times you may want a faster approx. and others a slower
more accurate calculation)
This decision will often be made for the user by the choice of field-types.
End users and app clients should be able to specify something like a bounding
box filter and get the most performant implementation w/o having to know if it
resolves to range queries, cartesian grids, or whatever.
fq={!gbox point=110,220 r=1.5} #specify a point and a radius
This does not necessarily preclude users from calling exact functions if they
know they are supported for that field 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.
