: For date faceting, count missing the order doesn't matter either, and : there it's given as a comma-separated list.
Either you are mistaken, or i don't understand your statement. date faceting works just like field faceting -- no comma seperated lists. : I think it makes sense doing everything in comma (or space) separated : lists, it's also "more" compatible with : other programming languages: : in many languages you can represent the GET variables as a dictionary, just about every (usable) langauge allows you to have "lists" as the value of a map (aka: dictionary). I'm adamantly opposed to adding any new params that have special "splitting" rules -- it imposes arbitrary and unneccessarsy limitations on the values thta you can pass to those params (unless you also have some "escaping" mechanism for the split character, but that just gets messy). x-url-form-encoding supports multivalued params for a reason. The only reason *any* existing solr params use comma or white space seperated lists is because way, way, WAY back in the day when it was just me and Yonik working on Solr at CNET, he was on the east coast working on the "guts" of Solr on the east coast, and i was on the west coast working on a meaty RequestHandler and we needed an API for modeling request params. Yonik put in a simple Map<String,String> and some code to populare it with ServletRequest params. I asked about multi value params for things like "fl" and some other faceting params i needed and he said something to the effect of "can't we just stringify the lists?" I didn't relaly know him that well yet, and i had about 45 more important features i needed him to implement, so i said "yeah, i guess" and resigned myself to never using anything but alphanumeric characters i nfield names. If Solr had been open source at the time, i would have just submitted a patch, and hounded him until he committed it :) : Using faceting.fields (plural) it could be backwards compatible. The problem with syntactic sugar like that, is that it breaks things like "defaults", "appends", and "invariant" params ... where by "break" i mean, not work the way the user expects/wants them to work without code in SolrParams jumping through a *lot* of hoops that i don't think anyone wants to write. -Hoss
