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

[jira] [Commented] (LUCENE-8894) Add APIs to tokenizer/charfilter/tokenfilter factories to get their SPI names from concrete classes

    [ https://issues.apache.org/jira/browse/LUCENE-8894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16886022#comment-16886022 ] 

Ignacio Vera commented on LUCENE-8894:
--------------------------------------

In master the entry in CHANGES.txt is in Lucene 9.0.0 bit from branch_8x the entry is under Lucene 8.3.0, is that correct?

 

> Add APIs to tokenizer/charfilter/tokenfilter factories to get their SPI names from concrete classes
> ---------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-8894
>                 URL: https://issues.apache.org/jira/browse/LUCENE-8894
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: modules/analysis
>            Reporter: Tomoko Uchida
>            Assignee: Tomoko Uchida
>            Priority: Minor
>             Fix For: master (9.0), 8.2
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Currently, reflection tricks are needed to obtain SPI name (this is now stored in static NAME fields in each factory class) from a concrete factory class. While it is easy to implement that logic, it would be much better to provide unified APIs to get SPI name from a factory class. In other words, the APIs would provide "inverse" operation of {{lookupClass(String)}} method.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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