[
https://issues.apache.org/jira/browse/SOLR-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703661#action_12703661
]
Ryan McKinley commented on SOLR-1131:
-------------------------------------
[TeeTokenFilter|http://lucene.apache.org/java/2_4_1/api/org/apache/lucene/analysis/TeeTokenFilter.html]
look interesting. How do you imagine it could help with letting a solr Field
index multiple fields?
Using the TeeTokenFilter seems like a matter of plumbing. Perhaps we could add
some properties to FieldType that create a SinkTokenizer and then use copyField
(or something similar) to use the existing SinkTokenizer.
I'm not familiar enought with the Sink/Tee stuff to know what we would need --
but we should make sure any SchemaField/FieldType changes open the door to this.
> Allow a single field to index multiple fields
> ---------------------------------------------
>
> Key: SOLR-1131
> URL: https://issues.apache.org/jira/browse/SOLR-1131
> Project: Solr
> Issue Type: New Feature
> Components: Analysis
> Reporter: Ryan McKinley
> Attachments: SOLR-1131-IndexMultipleFields.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.
