We've been building a UI which displays the results in a tabular formate, so
each of the fields that are available for search are presented to the user. We
still discussing where it's best to sort this out in our overall system design,
such as the UI or application layer. Given our current
OK, that makes sense. I'd deal with this on the UI side personally.
My reasoning is that it's poor design to make you search server
jump through hoops because you want to write client-side code
that can ignore edge cases. The UI changes and now you have
to go back to the search code to accommodate
You can use the Luke request handler to request all the fields in the
index, in case that helps with your UI. Solr's Schema Browser uses
that request handler to introspect. And Solr Flare also uses it to
figure out which fields to show as facets.
Erik
On Jan 28, 2010, at 10:08
This is kind of an unusual request, what higher-level
problem are you trying to solve here? Because the
field just *isn't there* in the underlying Lucene index
for that document.
I suppose you could index a not there token and just
throw those values out from the response...
Erick
On Wed, Jan
On 2010-01-28 03:21, Erick Erickson wrote:
This is kind of an unusual request, what higher-level
problem are you trying to solve here? Because the
field just *isn't there* in the underlying Lucene index
for that document.
I suppose you could index a not there token and just
throw those values
