This example loads two fictional components. Use spellcheck and clustering instead.
704 <requestHandler name="search" class="solr.SearchHandler" default="true"> 705 <!-- default values for query parameters can be specified, these 706 will be overridden by parameters in the request 707 --> 708 <lst name="defaults"> 709 <str name="echoParams">explicit</str> 710 <int name="rows">10</int> 711 </lst> 712 <!-- In addition to defaults, "appends" params can be specified 713 to identify values which should be appended to the list of 714 multi-val params from the query (or the existing "defaults"). 715 --> 716 <!-- In this example, the param "fq=instock:true" would be appended to 717 any query time fq params the user may specify, as a mechanism for 718 partitioning the index, independent of any user selected filtering 719 that may also be desired (perhaps as a result of faceted searching). 720 721 NOTE: there is *absolutely* nothing a client can do to prevent these 722 "appends" values from being used, so don't use this mechanism 723 unless you are sure you always want it. 724 --> 725 <!-- 726 <lst name="appends"> 727 <str name="fq">inStock:true</str> 728 </lst> 729 --> 730 <!-- "invariants" are a way of letting the Solr maintainer lock down 731 the options available to Solr clients. Any params values 732 specified here are used regardless of what values may be specified 733 in either the query, the "defaults", or the "appends" params. 734 735 In this example, the facet.field and facet.query params would 736 be fixed, limiting the facets clients can use. Faceting is 737 not turned on by default - but if the client does specify 738 facet=true in the request, these are the only facets they 739 will be able to see counts for; regardless of what other 740 facet.field or facet.query params they may specify. 741 742 NOTE: there is *absolutely* nothing a client can do to prevent these 743 "invariants" values from being used, so don't use this mechanism 744 unless you are sure you always want it. 745 --> 746 <!-- 747 <lst name="invariants"> 748 <str name="facet.field">cat</str> 749 <str name="facet.field">manu_exact</str> 750 <str name="facet.query">price:[* TO 500]</str> 751 <str name="facet.query">price:[500 TO *]</str> 752 </lst> 753 --> 754 <!-- If the default list of SearchComponents is not desired, that 755 list can either be overridden completely, or components can be 756 prepended or appended to the default list. (see below) 757 --> 758 <!-- 759 <arr name="components"> 760 <str>nameOfCustomComponent1</str> 761 <str>nameOfCustomComponent2</str> 762 </arr> 763 --> 764 </requestHandler> > would you please give me an example for custom request handler > > ----- > Thanks & Regards > Romi > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Problem-in-including-both-clustering-co > mponent-and-spellchecker-for-solr-search-results-at-the-same-e-tp3128864p31 > 28893.html Sent from the Solr - User mailing list archive at Nabble.com.
