[
https://issues.apache.org/jira/browse/SOLR-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14347335#comment-14347335
]
Kranti Parisa edited comment on SOLR-6492 at 3/4/15 6:42 PM:
-------------------------------------------------------------
Yes, so "my_field" will chose the analyzers based on the value of the field
"language"? If so, how are you planning to configure that mapping?
Example:
{code}
<field name="content" dynamicType="dynamic_field_type_one" indexed="true"
stored="true"/>
{code}
{code}
<dynamicFieldType name="dynamic_field_type_one">
<condition sourceFieldName="language" sourceFieldValue="en"
fieldType="text_en"/>
<condition sourceFieldName="language" sourceFieldValue="es"
fieldType="text_es"/>
<condition sourceFieldName="language" sourceFieldValue="ja"
fieldType="text_ja"/>
</dynamicFieldType>
{code}
so that we can pick up the fieldType for the field "content" based on the
values of another field "language". later stage sourceFieldValue could support
regex as well and we can introduce more params to the "condition" element. like
chose fieldType based on multiple field values etc..
We have dynamicField definitions already, why not dynamicFieldType?
This way we can reuse the "field" definitions except that instead of the "type"
param we have "dynamicType" and get the "fieldType" based on the condition.
once that is done, rest of the flow should be same as today to apply the
correct analyzers of that field type.
was (Author: krantiparisa):
Yes, so "my_field" will chose the analyzers based on the value of the field
"language"? If so, how are you planning to configure that mapping?
Example:
{code}
<field name="content" dynamicType="dynamic_field_type_one" indexed="true"
stored="true"/>
{code}
{code}
<dynamicFieldType name="dynamic_field_type_one">
<condition sourceFieldName="language" sourceFieldValue="en"
fieldType="text_en"/>
<condition sourceFieldName="language" sourceFieldValue="es"
fieldType="text_es"/>
<condition sourceFieldName="language" sourceFieldValue="ja"
fieldType="text_ja"/>
</dynamicFieldType>
{code}
so that we can pick up the fieldType for the field "content" based on the
values of another field "language". later stage sourceFieldValue could support
regex as well and we can introduce more params to the "condition" element. like
chose fieldType based on multiple field values etc..
We have dynamicField definitions already, why not dynamicFieldType?
> Solr field type that supports multiple, dynamic analyzers
> ---------------------------------------------------------
>
> Key: SOLR-6492
> URL: https://issues.apache.org/jira/browse/SOLR-6492
> Project: Solr
> Issue Type: New Feature
> Components: Schema and Analysis
> Reporter: Trey Grainger
> Fix For: 5.0
>
>
> A common request - particularly for multilingual search - is to be able to
> support one or more dynamically-selected analyzers for a field. For example,
> someone may have a "content" field and pass in a document in Greek (using an
> Analyzer with Tokenizer/Filters for German), a separate document in English
> (using an English Analyzer), and possibly even a field with mixed-language
> content in Greek and English. This latter case could pass the content
> separately through both an analyzer defined for Greek and another Analyzer
> defined for English, stacking or concatenating the token streams based upon
> the use-case.
> There are some distinct advantages in terms of index size and query
> performance which can be obtained by stacking terms from multiple analyzers
> in the same field instead of duplicating content in separate fields and
> searching across multiple fields.
> Other non-multilingual use cases may include things like switching to a
> different analyzer for the same field to remove a feature (i.e. turning
> on/off query-time synonyms against the same field on a per-query basis).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
