You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Tomoko Uchida (JIRA)" <ji...@apache.org> on 2019/07/01 14:28:00 UTC

[jira] [Updated] (SOLR-13593) Allow to specify analyzer components by their SPI names in schema definition

     [ https://issues.apache.org/jira/browse/SOLR-13593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomoko Uchida updated SOLR-13593:
---------------------------------
    Description: 
Now each analysis factory has explicitely documented SPI name which is stored in the static "NAME" field (LUCENE-8778).
 Solr uses factories' simple class name in schema definition (like class="solr.WhitespaceTokenizerFactory"), but we should be able to also use more concise SPI names (like name="whitespace").

e.g.:
{code:xml}
<fieldtype name="myfieldtype" class="solr.TextField">
  <analyzer>
    <tokenizer class="solr.WhitespaceTokenizerFactory"/>
    <filter class="solr.KeywordMarkerFilterFactory" protected="protwords.txt" />
    <filter class="solr.PorterStemFilterFactory" />
  </analyzer>
</fieldtype>
{code}
would be
{code:xml}
<fieldtype name="myfieldtype" class="solr.TextField">
  <analyzer>
    <tokenizer name="whitespace"/>
    <filter class="keywordMarker" protected="protwords.txt" />
    <filter class="porterStem" />
  </analyzer>
</fieldtype>
{code}

  was:
Now each analysis factory has explicitely documented SPI names which is stored in the static "NAME" field (LUCENE-8778).
 Solr uses factories' simple class name in schema definition (like class="solr.WhitespaceTokenizerFactory"), but we should be able to also use more concise SPI names (like name="whitespace").

e.g.:
{code:xml}
<fieldtype name="myfieldtype" class="solr.TextField">
  <analyzer>
    <tokenizer class="solr.WhitespaceTokenizerFactory"/>
    <filter class="solr.KeywordMarkerFilterFactory" protected="protwords.txt" />
    <filter class="solr.PorterStemFilterFactory" />
  </analyzer>
</fieldtype>
{code}
would be
{code:xml}
<fieldtype name="myfieldtype" class="solr.TextField">
  <analyzer>
    <tokenizer name="whitespace"/>
    <filter class="keywordMarker" protected="protwords.txt" />
    <filter class="porterStem" />
  </analyzer>
</fieldtype>
{code}


> Allow to specify analyzer components by their SPI names in schema definition
> ----------------------------------------------------------------------------
>
>                 Key: SOLR-13593
>                 URL: https://issues.apache.org/jira/browse/SOLR-13593
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Schema and Analysis
>            Reporter: Tomoko Uchida
>            Priority: Major
>
> Now each analysis factory has explicitely documented SPI name which is stored in the static "NAME" field (LUCENE-8778).
>  Solr uses factories' simple class name in schema definition (like class="solr.WhitespaceTokenizerFactory"), but we should be able to also use more concise SPI names (like name="whitespace").
> e.g.:
> {code:xml}
> <fieldtype name="myfieldtype" class="solr.TextField">
>   <analyzer>
>     <tokenizer class="solr.WhitespaceTokenizerFactory"/>
>     <filter class="solr.KeywordMarkerFilterFactory" protected="protwords.txt" />
>     <filter class="solr.PorterStemFilterFactory" />
>   </analyzer>
> </fieldtype>
> {code}
> would be
> {code:xml}
> <fieldtype name="myfieldtype" class="solr.TextField">
>   <analyzer>
>     <tokenizer name="whitespace"/>
>     <filter class="keywordMarker" protected="protwords.txt" />
>     <filter class="porterStem" />
>   </analyzer>
> </fieldtype>
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org