On 2/9/07, Erik Hatcher <[EMAIL PROTECTED]> wrote:
On Feb 9, 2007, at 9:16 PM, Mike Klaas wrote: > Might I suggest: > > filter.query > filter.term > filter.<future expansion> I like it. While Hoss has a point, though descriptive names do make a lot of sense too. It has been a bit confusing to explain facet.query and fq as two different things.
I like self-documenting parameter names, but if there is concern about verbosity, how 'bout: fq fq.term (also, filter.q could be used in the longer version). As for future expansion, some possibilities are: filter.op/filter.q.op (set operator of filter query parser, which is currently OR regardless of the solrconfig setting), filter.range, and filter.q.noncached (something I would definitely use if it existed).
However, is there any concern, at all, about the added overhead in passing larger requests around?
I would guess that the difference would be impossible to measure, but I don't really know. -Mike
