[ 
http://issues.apache.org/jira/browse/SOLR-73?page=comments#action_12454132 ] 
            
Yonik Seeley commented on SOLR-73:
----------------------------------

Related topic: 
http://www.nabble.com/making-schema.xml-nicer-to-read-use-tf2148401.html#a5932524

I'll buy long-names for implementations of things specified in solrconfig.xml
Average users aren't going to be switching classes in solrconfig.xml anyway.

For tokenizer/filter specifications in the schema, however, long class names 
for standard filters just makes it harder to read and forces more lines to wrap 
around while viewing.  Readability here is key, since people will be switching 
around and customizing the arguments to filters.

Would it be better if we just left off the "solr" alias, so one could specify 
"LowercaseFilter" and get a LowercaseFilter?

> schema.xml and solrconfig.xml use CNET-internal class names
> -----------------------------------------------------------
>
>                 Key: SOLR-73
>                 URL: http://issues.apache.org/jira/browse/SOLR-73
>             Project: Solr
>          Issue Type: Bug
>          Components: search
>            Reporter: Walter Underwood
>
> The configuration files in the example directory still use the old 
> CNET-internal class names, like solr.LRUCache instead of 
> org.apache.solr.search.LRUCache.  This is confusing to new users and should 
> be fixed before the first release.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to