[
https://issues.apache.org/jira/browse/SOLR-2663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067273#comment-13067273
]
Robert Muir commented on SOLR-2663:
-----------------------------------
{quote}
Regardless of my usecase, i think this is a good idea in general since it makes
IndexSchema a lot easier to read/maintain and helps make it more obvious
exactly what info is being used when initializing the FieldTypes+Analyzers
{quote}
+1, I find it hard to navigate this class, I think it helps to split it up.
> Refactor FieldTypePluginLoader out of IndexSchema
> -------------------------------------------------
>
> Key: SOLR-2663
> URL: https://issues.apache.org/jira/browse/SOLR-2663
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Assignee: Hoss Man
> Attachments: SOLR_2663.patch
>
>
> I have a use case where i'd like to be able to programmaticly "test" if a
> (single) arbitrary FieldType configuration is valid, but this is currently
> impossibly because the code to parse/init FieldTypes is buried deep inside
> IndexSchema.readSchema using anonymous inner-subclasses of
> AbstractPluginLoader.
> I'd like to refactor this out into a concrete public class. Regardless of my
> usecase, i think this is a good idea in general since it makes IndexSchema a
> lot easier to read/maintain and helps make it more obvious exactly what info
> is being used when initializing the FieldTypes+Analyzers
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
