[
https://issues.apache.org/jira/browse/SOLR-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514860
]
Hoss Man commented on SOLR-314:
-------------------------------
I'm on the same page with the first part of JJs comments, the API seems a
awkward and forced. adding a new analyzer type would be one way to go if we
wanted to change things at the schema/doc-processing level -- the approach i
was thinking about was just anew FieldType that used it's index analyzer for
the stored values as well as the indexed values.
i'm not really understanding most of the dicsussion about concatenating and how
that would work -- but i see it as being largely unrelated to the main point of
the issue (a way to tokenize and process an input string) because people may
want to use an option like that even when sending discrete values -- we should
tackle the issues seperately
> Store Analyzed token text from an incoming SolrInputDocument
> ------------------------------------------------------------
>
> Key: SOLR-314
> URL: https://issues.apache.org/jira/browse/SOLR-314
> Project: Solr
> Issue Type: New Feature
> Components: update
> Reporter: Ryan McKinley
> Attachments: SOLR-314-StoreAnalysis.patch
>
>
> This is an UpdateRequestProcessor that runs incoming fields through a Field
> Analyzer and stores the output of each token as a field value.
> For Example. If you have a field type defined:
> <fieldType name="text_ws" class="solr.TextField" >
> <analyzer>
> <tokenizer class="solr.WhitespaceTokenizerFactory"/>
> </analyzer>
> </fieldType>
> And send a request:
> /update?store.analysis=true&f.feature.analysis=text_ws
> <add> <doc>
> <field name="feature">aaa bbb ccc</field>
> </doc></add>
> The returned document will look like:
> <doc>
> <arr name="feature">
> <str>aaa</str>
> <str>bbb</str>
> <str>ccc</str>
> </arr>
> </doc>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
