Good point, I was proposing it as an alternative to myfield_facet since that seems to overload the field name a bit too much. I agree that solrconfig + specialized request handlers are a much better location for that kind of stuff.
Also, the reason other engines require you to mark the fields in the index definition is because they actually index the data differently if it is a facet vs a normal indexed field. It's cool that solr doesn't have to do this but there may be a case where it would be a good idea someday. - will -----Original Message----- From: Chris Hostetter [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 23, 2007 6:34 PM To: Solr Dev Subject: RE: [jira] Commented: (SOLR-247) Allow facet.field=* to facet on all fields (without knowing what they are) : What about adding an optional parameter to the field definition in the : IndexSchema for defaultFacet="true/false". This would make solr's information should go in schema.xml if the are inherient to the data and the physical index. Things should go in the solrconfig.xml if they relate to how the index is used -- a master might have a differnet solrconfig then a slave because it doesn't get used for queries, while two diffenret slaves might have differnet solrconfigs because they get used by different sets of clients and need differnet cache configs or request handler configs -- but all three would use the same schema.xml because the physical index is the same in all cases. a mechanism already exists to say "by default, i want clients to get facets on certian fields" in teh solrconfig.xml, it's just a default param for hte requestHandler ... <requestHandler name="standard" class="solr.StandardRequestHandler"> <!-- default values for query parameters --> <lst name="defaults"> <str name="facet.field">category</str> <str name="facet.field">author</str> <str name="facet.field">type</str> ... ...then the params are defaulted for everyone, and the only thingthe user needs in the URL is "facet=true" ... or that can be defaulted as well. -Hoss
