Erik Hatcher wrote:
On May 22, 2007, at 10:42 PM, Ryan McKinley wrote:
If thats the case, I think the .diff you posted is fine...
Not really, because I commented out a bit to get past things. It was
more than just setting the default to zero.
the bit you commented calculated numTerms across all fields (forcing it
to walk through all terms) since this is not all that useful and
configuring it seems overkill, I don't mind throwing it out.
I'll take a look and make sure though.
The only thing I would change is I think the default should be some
positive number. For the app where you want the default to be 0, you
can initialize the request handler with:
<requestHandler ... >
<lst name="defaults">
<int name="numTerms">0</int>
</lst>
</requestHandler>
I don't get why the default should be non-zero. The most common use
case would be field/type/size introspection, I presume.
I have been using it as a visual inspection of what it in the index.
The default page that shows all information for all fields is good
because (without figuring out what parameters do what) you can just see
what is in the index... for the indexes I have worked with (so far
<300K docs) that has been fine.
Luke (the app) opens showing top terms across all fields - then you
click on individual fields to see the top terms for that field.
I would like the default (no params / no config) be the most useful to
people who are just starting with lucene/solr and want to know what all
this talk about "terms" is.
programmatic uses can easily send "numTerms=0" in the request or
configure it in the defaults.
I don't see
getting top terms being as needed. But, I'm fine with the default being
non-zero if others feel it should be - setting it in the config file is
no big deal for me :)
Erik
