[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788802#action_12788802
]
Yonik Seeley commented on SOLR-1131:
------------------------------------
bq. Yonik, could you elaborate on this? It seems kind of weird to have that
instanceof check in SolrQueryParser.getFieldQuery() to see if we have a
TextField or not.
If you look at the impl in TextField, I had to comment out stuff like
"newTermQuery" and replace it with "new TermQuery".
+ // Query currentQuery = newTermQuery(new Term(field, term));
+ Query currentQuery = new TermQuery(new Term(field, term));
To be fully back compatible, all we would need to do is check if the parser was
an instance of QueryParser, and if so, delegate to newTermQuery. Then we could
use fieldType.getFieldQuery() absolutely everywhere.
> 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,
> 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.
