[
https://issues.apache.org/jira/browse/LUCENE-8894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomoko Uchida updated LUCENE-8894:
----------------------------------
Description: 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 "reverse" operation of
{{lookupClass(String)}} method. (was: 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.)
> 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
>
> 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 "reverse" operation of {{lookupClass(String)}} method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
