: Facets are slightly different than docfreq's... one is expensive, and
: one is very cheap since it's pre-calculated by lucene.
: If you want to page through or download *all* terms of a full-text
: field, the faceting code would take forever in comparison.
i was thinking the same thing.
: "index" : {
: "numDocs" : 10123,
: "maxDoc" : 12345,
: "age" : 2000, #number of milliseconds the index has been open... sort of
equivalent to index freshness, but not really.
: "version":123425235, #index version. Actually, I think this should be in
responseHeader to aid in client-side caching
: }
:
: I think this stuff is useful, it's just a matter of preference if it
: goes in the same handler or not. If this *does* go in this handler, then
: perhaps it should be named "indexinfo" or something. I'd be fine with
: this hander being only about schema too though.
+1 to all of that ... "IndexInfo" seeems like a good thing for returning
all sorts of info, of which the field list is just one piece ... I think
adding the stuff yonik listed above definitely makes sense in the same
request handler that reutrns the list of fields ... the TermEnum iteration
with docFreq might make more sense in a seperate request handler if for no
other reason then to simplify the API when paginating through terms
-Hoss
