On Feb 12, 2008, at 3:44 PM, Grant Ingersoll wrote:
On Feb 12, 2008, at 2:10 PM, Chris Hostetter wrote:
: > 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.
but why does your client/display care which field is the uniqueKey
field?
knowing which fields it might query or ask for in the fl list sure
-- but
why need to know about hte uniqueKey field specificly?
How do I generate URLs to retrieve a document against any given
Solr instance that I happen to be pointing at without knowing which
field is the document id?
One cool technique, not instead of your change to Luke RH (a needed
change IMO) but another way to go about it - we have a
DocumentRequestHandler that takes a uniqueKey parameter that would
retrieve and return that single document without having to specify
the field name explicitly.
Erik
