[ 
https://issues.apache.org/jira/browse/SOLR-2397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man updated SOLR-2397:
---------------------------

    Attachment: solrconfig.xml
                SOLR-2397.patch

patch against trunk to do all of hte cleanup i think we should do.

for readability, i've also attached the finished solrconfig.xml

the main change here is reformatting all of hte xml and comments to have 
standard indenting, and reformating all the comments to use standard line 
length.

i also re-organized things so all request handlers are listed together (and all 
update handlers are listed together within that list) the only exception is hte 
one off handlers declared just to show off an individual search component -- 
those i left next to the component.

i also enhanced the comments where i thought they made sense.

> main example solrconfig.xml needs cleanup before 3.1
> ----------------------------------------------------
>
>                 Key: SOLR-2397
>                 URL: https://issues.apache.org/jira/browse/SOLR-2397
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>            Assignee: Hoss Man
>             Fix For: 3.1, 4.0
>
>         Attachments: SOLR-2397.patch, solrconfig.xml
>
>
> the main solconfig.xml example file has gotten cluttered, doesn't use 
> consistent indenting, lists various things in a haphazard order, and contains 
> relics of outdated/deprecated plugins/terminology.  this really needs to be 
> dealt with prior to 3.1 since most people reuse this example as the basis for 
> their own configs.
> rather then trying to opening individual issues for little one off changes 
> (which is how a lot of the haphazard came about) i'm going to take a stab at 
> one big cleanup here and seek feedback on the end result

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to