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/06/23 13:03:00 UTC
[jira] [Updated] (LUCENE-8874) Show SPI names only instead of class
names in Luke Analysis tab
[ https://issues.apache.org/jira/browse/LUCENE-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomoko Uchida updated LUCENE-8874:
----------------------------------
Description:
Each analyzer component factory now has an explicitly documented "NAME" static field (LUCENE-8778) to promote the proper use of (symbolic) SPI names.
It would be better to get rid of all concrete factory class names from the Analysis tab UI, but instead show SPI names.
From implementation perspective, reflection tricks are needed to obtain the {{NAME}} field value without knowing the concrete classes (frameworks like Luke Analysis tab often don't know them). APIs to obtain the SPI name from a factory object might be needed for convenience and unified access to the names.
was:
Each analyzer component factory now has an explicitly documented "NAME" static field (LUCENE-8778) to promote the proper use of (symbolic) SPI names.
It would be better to get rid of all concrete factory class names from the Analysis tab, and instead, show SPI names.
From implementation perspective, reflection tricks are needed to obtain the {{NAME}} field value without knowing the concrete class (frameworks like Luke Analysis tab often don't know it). APIs to obtain the SPI name from a factory object might be needed for convenience and unified access to the names.
> Show SPI names only instead of class names in Luke Analysis tab
> ---------------------------------------------------------------
>
> Key: LUCENE-8874
> URL: https://issues.apache.org/jira/browse/LUCENE-8874
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/analysis, modules/luke
> Reporter: Tomoko Uchida
> Priority: Minor
>
> Each analyzer component factory now has an explicitly documented "NAME" static field (LUCENE-8778) to promote the proper use of (symbolic) SPI names.
> It would be better to get rid of all concrete factory class names from the Analysis tab UI, but instead show SPI names.
> From implementation perspective, reflection tricks are needed to obtain the {{NAME}} field value without knowing the concrete classes (frameworks like Luke Analysis tab often don't know them). APIs to obtain the SPI name from a factory object might be needed for convenience and unified access to the names.
--
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