On Feb 11, 2008, at 11:24 PM, Chris Hostetter wrote:
: Another option is to add it to the responseHeader???? Or it could
be a quick
: add to the LukeRH. The former has the advantage that we wouldn't
have to make
adding the info to LukeRequestHandler makes sense.
Honestly: i can't think of a single use case where client code would
care
about what the uniqueKey field is, unless it already *knew* what the
uniqueKey field is.
:-) Abstractions allow one to use different implementations. My
client/display doesn't know about Solr, it just knows it can search
and the Solr implementation part of it can be pointed at any Solr
instance (or other search engines as well), thus it needs to be able
to "reflect" on Solr. The unique key is a pretty generally useful
thing across implementations.
In fact, I wish all the ReqHandlers had an introspection option, where
one could see what params are supported as well.
: Of course, it probably would be useful to be able to request the
schema from
: the server and build an IndexSchema object on the client side.
This could be
: added to the LukeRH as well.
somebody was working on that at some point ... but i may be thinking
of
the Ruby client ... no.... i'm pretty sure i remember it coming up
in the
context of Java because i remember dicsussion that a full
"IndexSchema"
was too much because it required the client to have the class files
for
all of the analysis chain and filedtype classes.
It may be reasonable, as a compromise, to just have metadata about
these things. Sort of like BeanInfo provides.
-Grant
